From: Lars Ingebrigtsen <larsi@gnus.org>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: 14322@debbugs.gnu.org
Subject: bug#14322: 24.3; emacsclient -c behavior regression
Date: Sun, 06 Dec 2020 16:55:34 +0100 [thread overview]
Message-ID: <87eek37wuh.fsf@gnus.org> (raw)
In-Reply-To: <517FE7CE.1060408@thregr.org> (Yuri D'Elia's message of "Tue, 30 Apr 2013 17:48:30 +0200")
Yuri D'Elia <wavexx@thregr.org> writes:
> I think this is a regression in emacs24 (lucid), because this used to
> work under emacs23:
>
> If you start emacs --daemon
>
> and you have the following:
>
> (add-hook 'after-make-frame-functions
> (lambda (frame)
> (print (display-graphic-p))))
>
> and you create a new frame via:
>
> emacsclient -c
>
> you will notice that the result is always 'f'.
(This bug report unfortunately got no response at the time.)
The result is always nil, yes -- but if you use the frame as a parameter
to that function, you get the correct results:
(setq after-make-frame-functions
(list
(lambda (frame)
(message "frame: %s %s" frame (display-graphic-p frame)))))
./lib-src/emacsclient -c
frame: #<frame GNU Emacs at xo 0x5574a438f338> t
> Not only that, but any frame manipulation will cause the daemon to crash.
>
> emacsclient -e '(make-frame)'
This seems to be fixed, though. It now just reports an error:
*ERROR*: Unknown terminal type
So I think everything here works as designed, and I'm closing this bug
report. If there's more to be done here, please respond to the debbugs
address and we'll reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-12-06 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 15:48 bug#14322: 24.3; emacsclient -c behavior regression Yuri D'Elia
2020-12-06 15:55 ` Lars Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eek37wuh.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=14322@debbugs.gnu.org \
--cc=wavexx@thregr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.