bug#21123: emacsclient silently eats keys on startup

bug#21123: emacsclient silently eats keys on startup

[William Hatch]

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

When emacsclient is launched with -t (terminal mode), there is a short time
when I press keys and they have no effect.  Most commonly this happens when
I open a file knowing that I want to search for something, so I immediately
type backslash (bound to evil-search-forward), then the text I want to
search for.  When the slash and potentially some of the search term are
eaten, strange things happen when emacs suddenly starts interpreting the
middle of this key sequence as the start of it.

This doesn't happen when emacs is started normally in a terminal.  One of
my favorite things about using a terminal is that I can type ahead when I
know what I'm doing, and I don't have to wait for the GUI to catch up to
me.  Emacsclient breaks this, and it is especially noticeable over ssh.  I
have confirmed that this happens with no init file, so I'm sure it's not
just something in my configuration.

Confirmed in emacs versions 24.5.50.1 and 25.0.50.1.

Thanks (emacs is the best),
William

[-- Attachment #2: Type: text/html, Size: 1116 bytes --]

bug#21123: emacsclient silently eats keys on startup

[Andreas Schwab]

William Hatch <willghatch@gmail.com> writes:

> When emacsclient is launched with -t (terminal mode), there is a short time
> when I press keys and they have no effect.

How short is that time?  I couldn't reproduce it when trying this:

$ sleep 5; emacsclient -t

and then starting to type ahead.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

bug#21123: emacsclient silently eats keys on startup

[William G Hatch]

On Fri, Jul 24, 2015 at 09:08:17AM +0200, Andreas Schwab wrote:
>William Hatch <willghatch@gmail.com> writes:
>
>> When emacsclient is launched with -t (terminal mode), there is a short time
>> when I press keys and they have no effect.
>
>How short is that time?  I couldn't reproduce it when trying this:
>
>$ sleep 5; emacsclient -t
>
>and then starting to type ahead.

Interestingly I can't reproduce it that way either... so maybe it has to be at
the exact time emacs is starting up.  On a new machine locally I have to be
pretty quick to reproduce it, but it's still something I'll occasionally accidentally
do, but it happens more often over ssh.  It seems to happen during the time that
emacsclient still shows the scratch buffer but before it opens up the file I tell
it to open.  But the keys don't go to the scratch buffer either, so I'm not sure
what's going on.

It's hard to get to work with an empty init file -- it happens more when
there are mode hooks or something that run when emacsclient opens a file.

bug#21123: emacsclient silently eats keys on startup

[Marcin Borkowski]

On 2015-07-24, at 09:17, William G Hatch <willghatch@gmail.com> wrote:

> On Fri, Jul 24, 2015 at 09:08:17AM +0200, Andreas Schwab wrote:
>>William Hatch <willghatch@gmail.com> writes:
>>
>>> When emacsclient is launched with -t (terminal mode), there is a short time
>>> when I press keys and they have no effect.
>>
>>How short is that time?  I couldn't reproduce it when trying this:
>>
>>$ sleep 5; emacsclient -t
>>
>>and then starting to type ahead.
>
> Interestingly I can't reproduce it that way either... so maybe it has to be at
> the exact time emacs is starting up.  On a new machine locally I have to be
> pretty quick to reproduce it, but it's still something I'll occasionally accidentally
> do, but it happens more often over ssh.  It seems to happen during the time that
> emacsclient still shows the scratch buffer but before it opens up the file I tell
> it to open.  But the keys don't go to the scratch buffer either, so I'm not sure
> what's going on.
>
> It's hard to get to work with an empty init file -- it happens more when
> there are mode hooks or something that run when emacsclient opens a file.

Hi,

just asking: does this persist?  If yes, can you give a recipe for
reproducing it, possibly starting with emacs -Q?

Best,

-- 
Marcin

bug#21123: emacsclient silently eats keys on startup

[Stefan Kangas]

Marcin Borkowski <mbork@mbork.pl> writes:

> On 2015-07-24, at 09:17, William G Hatch <willghatch@gmail.com> wrote:
>
>> On Fri, Jul 24, 2015 at 09:08:17AM +0200, Andreas Schwab wrote:
>>>William Hatch <willghatch@gmail.com> writes:
>>>
>>>> When emacsclient is launched with -t (terminal mode), there is a short time
>>>> when I press keys and they have no effect.
>>>
>>>How short is that time?  I couldn't reproduce it when trying this:
>>>
>>>$ sleep 5; emacsclient -t
>>>
>>>and then starting to type ahead.
>>
>> Interestingly I can't reproduce it that way either... so maybe it has to be at
>> the exact time emacs is starting up.  On a new machine locally I have to be
>> pretty quick to reproduce it, but it's still something I'll occasionally accidentally
>> do, but it happens more often over ssh.  It seems to happen during the time that
>> emacsclient still shows the scratch buffer but before it opens up the file I tell
>> it to open.  But the keys don't go to the scratch buffer either, so I'm not sure
>> what's going on.
>>
>> It's hard to get to work with an empty init file -- it happens more when
>> there are mode hooks or something that run when emacsclient opens a file.
>
> Hi,
>
> just asking: does this persist?  If yes, can you give a recipe for
> reproducing it, possibly starting with emacs -Q?

More information was requested, but none was given within 3 years, so
I'm closing this bug report.  If this is still an issue, please reopen
this bug report.

Best regards,
Stefan Kangas