From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 35058@debbugs.gnu.org, agrambot@gmail.com
Subject: bug#35058: [PATCH] Use display-graphic-p in more cases
Date: Sat, 06 Apr 2019 10:18:40 +0300 [thread overview]
Message-ID: <83y34na9f3.fsf@gnu.org> (raw)
In-Reply-To: <558890e4-a519-48ec-8e9d-36d829a5c089@default> (message from Drew Adams on Mon, 1 Apr 2019 07:32:23 -0700 (PDT))
> Date: Mon, 1 Apr 2019 07:32:23 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 35058@debbugs.gnu.org
>
> This is a great description, Eli.
>
> I hope it or similar is recorded somewhere in
> code or code-related artifacts, not just in
> mail threads.
Thanks, I added commentary to frame.el, where these functions are
defined.
> BTW, where would the intended meaning of such
> functions be recorded now? Currently their
> doc is just the doc of `display-graphic-p',
> as they are aliased. (Could/should they have
> their own doc strings now, even if the behavior
> is currently just `display-graphic-p'?)
I don't think we have features to have separate doc strings for them,
I hope the commentary I wrote is enough.
next prev parent reply other threads:[~2019-04-06 7:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 23:38 bug#35058: [PATCH] Use display-graphic-p in more cases Alex
2019-03-31 12:45 ` Basil L. Contovounesios
2019-03-31 15:37 ` Eli Zaretskii
2019-04-01 4:15 ` Alex
2019-04-01 5:21 ` Eli Zaretskii
2019-04-02 17:05 ` Alex
2019-04-02 17:23 ` Eli Zaretskii
2019-04-02 17:57 ` Alex
2019-04-02 18:39 ` Eli Zaretskii
2019-04-03 5:14 ` Alex
2019-04-03 5:29 ` Eli Zaretskii
2019-04-03 20:26 ` Alex
2019-04-05 7:29 ` Eli Zaretskii
2019-04-05 16:35 ` Alex
2019-04-05 18:51 ` Eli Zaretskii
2019-04-07 5:11 ` Alex
[not found] ` <<83a7hagv11.fsf@gnu.org>
2019-04-01 14:32 ` Drew Adams
2019-04-06 7:18 ` Eli Zaretskii [this message]
2019-04-07 13:50 ` Stefan Monnier
[not found] <<8736n4ndav.fsf@gmail.com>
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=83y34na9f3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35058@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=drew.adams@oracle.com \
/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.