Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove unnecessary input win redisplay #1948

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

H3rnand3zzz
Copy link
Contributor

  • I ran valgrind when using my new feature

How to test the functionality

  • Use /editor and write some stuff, after this save and close, input should be updated.

The redisplay function in keyboard handling event was introduced by @rodarima
in the following commit:
7eac636

At the point first commit introduction it made sense, but later
the following commit added proper handling of input redisplay.
ccede06

This change was overlooked by me and introduced in profanity-im#1943.

Potential solution for profanity-im#1947.
@jubalh jubalh added this to the next milestone Jan 19, 2024
@jubalh jubalh merged commit 11762fd into profanity-im:master Jan 19, 2024
6 checks passed
jubalh added a commit that referenced this pull request Feb 19, 2024
Revert "Merge pull request #1943 from H3rnand3zzz/gmainloop

This reverts commit 609fde0, reversing
changes made to 2ec9406.

Revert "Merge pull request #1948 from H3rnand3zzz/fix/rl-less-refreshes"

This reverts commit 11762fd, reversing
changes made to 609fde0.

We have got several issues, that we don't quite see how to solve, with
the merge of the gmainloop PR.

* Slashguard is broken (#1955) (though #1956 could fix that)
* One person reported problems with copy paste selection via mouse
* Some input buffer seems not to be cleared correctly
  It happened that I was debugging profanity used `/connect` and typed
  the password. I then debugged so long that a time out occurred, so
  profanity disconnected. Then it printed "unknown command: $password".

There was something else that I forgot now.

Bottomline is: so far we didn't get it right so we will undo these
changes until someone proposes a working solution.

We got a slight performance increase (apparently noticable when
alt+mouse scrolling) but got too many issues with this change.
@jubalh
Copy link
Member

jubalh commented Feb 19, 2024

Undone in 88b26cf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants