Timeline for How can I prevent `84;0;0c` written into first line when emacs daemon starts running?
Current License: CC BY-SA 4.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 22, 2022 at 9:42 | comment | added | alper | @NickD done hope my answer will be helpful | |
| Jun 22, 2022 at 9:41 | vote | accept | alper | ||
| Jun 22, 2022 at 9:41 | answer | added | alper | timeline score: 2 | |
| Jun 22, 2022 at 1:54 | comment | added | NickD | Write it up as an answer and accept it (after the waiting period). | |
| Jun 21, 2022 at 19:22 | comment | added | alper |
@NickD my problem was related to following question: emacs.stackexchange.com/questions/16878/… . Seems like I just had to do: (setq xterm-extra-capabilities nil)
|
|
| S Jun 16, 2022 at 15:00 | history | bounty ended | CommunityBot | ||
| S Jun 16, 2022 at 15:00 | history | notice removed | CommunityBot | ||
| Jun 11, 2022 at 13:23 | comment | added | alper | issuing at emacs repo? Should I ask this question in unix.stackexchange.com since seems like this issue could be resolved by correct usage of linux commands | |
| Jun 10, 2022 at 21:01 | comment | added | NickD |
FWIW, I guess somebody is issuing an ANSI escape sequence (e.g. 'ESC [ 84;0;0c) but I cannot find one that ends in c`.
|
|
| Jun 10, 2022 at 20:58 | comment | added | NickD |
What do the emacsclient options -qut do? I don't find them in my emacsclient man page at all. As for "starting the emacs daemon", I don't understand what you mean: emacsclient cannot start the daemon - instead you start emacs with --daemon and it runs in the background without a frame, but starts a server to listen. Then you invoke emacsclient to connect to the server. In short, I don't think you are describing the situation you are facing accurately enough, so nobody can figure out what's really happening, let alone fix it.
|
|
| Jun 10, 2022 at 13:27 | comment | added | alper |
@TianshuWang This is not related to zsh ; it happens with bash as well.
|
|
| Jun 10, 2022 at 13:06 | comment | added | Tianshu Wang | I suggest you divide and test your Emacs and ZSH related config. | |
| Jun 10, 2022 at 13:02 | comment | added | Tianshu Wang | I don't have this problem on macOS, iTerm2 and Emacs 28.1 | |
| Jun 9, 2022 at 16:28 | comment | added | alper | I am using iTerm2(iterm2.com) ; same problem occurs in Terminal | |
| Jun 9, 2022 at 0:48 | comment | added | db48x | This is probably not an Emacs problem. What terminal emulator are you using? Do you get the same results if you use xterm instead? | |
| Jun 8, 2022 at 13:24 | history | edited | alper | CC BY-SA 4.0 |
added 3 characters in body
|
| S Jun 8, 2022 at 13:15 | history | bounty started | alper | ||
| S Jun 8, 2022 at 13:15 | history | notice added | alper | Authoritative reference needed | |
| Jun 8, 2022 at 13:11 | history | edited | alper | CC BY-SA 4.0 |
added 73 characters in body
|
| Jun 8, 2022 at 13:09 | comment | added | alper |
@Tobias I figure out the reason for this. I was starting emacs daemon as follows: emacsclient -qut 2>/dev/null after this when I press any key like enter that writting into 1st line of the open file followed by 84;0;0c
|
|
| May 25, 2022 at 18:32 | comment | added | alper | Yes but when emacs freeze and when I try to exit from the daemon or press some keys they written into buffer and shows up after the emacs starts working | |
| May 20, 2022 at 12:34 | comment | added | Tobias |
Have you tried to interrupt Emacs from some shell command line via pkill -SIGUSR2 emacs? That should start the debugger. It may be necessary to call pkill -SIGUSR2 emacs multiple times.
|
|
| May 20, 2022 at 10:38 | history | asked | alper | CC BY-SA 4.0 |