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

Wrong type argument #10

Open
sebastiencs opened this issue Jun 9, 2017 · 5 comments
Open

Wrong type argument #10

sebastiencs opened this issue Jun 9, 2017 · 5 comments

Comments

@sebastiencs
Copy link

Hi, When I run restart-emacs, I got this error:
Wrong type argument: processp, nowait
It's in the function restart-emacs--record-tty-file (i'm using emacs GUI)
The parameter current is set to (client . nowait)

I have attached the backtrace if it can help
backtrace.txt

@iqbalansari
Copy link
Owner

Hi @sebastiencs,

Thanks a lot for the detailed bug report. I have just pushed a fix for the issue, could you please try it once MELPA updates and report back if the issue still occurs

Thanks

@sebastiencs
Copy link
Author

sebastiencs commented Jun 10, 2017

Thank you for this quick fix. It resolves the error.

Now I have another problem:
Once emacs is restarted, when I quit emacsclient with C-x C-c (save-buffers-kill-terminal) the daemon is also ended. I have to start it again.
This problem appears only with emacs GUI, it works with emacs on terminal (I have 2 differents daemons for each)

Also, I don't know if it's important but I have this message in the *Warnings* buffer:
Error (frameset): Unknown terminal type

I don't know what information can I give you to help you, let me know if you need something

@iqbalansari
Copy link
Owner

That seems like a bug, I have an idea why it happens, will try pushing a fix soon. Thanks for the report

@dinkonin
Copy link

I have the same problem using emacs in daemon mode, when I restart it I also get

Error (frameset): Unknown terminal type

the daemon does not start again and needs to be started manually.

I'm using emacs 25.2.1 on ArchLinux

@iqbalansari
Copy link
Owner

@dinkonin @sebastiencs There does not seem to be a way to fix the issue, I will keep looking though. I am keeping this issue open as a reminder

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

No branches or pull requests

3 participants