unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: how to use graphic-display-p and window-system
Date: Fri, 17 Apr 2009 10:37:45 -0700	[thread overview]
Message-ID: <001a01c9bf83$38bd2270$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <834owro4ha.fsf@gnu.org>

> From: Eli Zaretskii Sent: Tuesday, April 14, 2009 4:33 AM
> To: 2993@emacsbugs.donarmstrong.com Subject: bug#2993
> > posn-col-row uses the `line-spacing' value in terminals.  
> > According to the doc `line-spacing' only has an effect
> > in window systems.
> 
> You mean, on graphic displays. Please use `display-graphic-p' 
> rather than assuming that if `window-system' is non-nil, the 
> display is necessarily a graphic one. At least one Emacs 
> configuration violates this assumption.

I'm not familiar with `display-graphic-p'. I've been using `window-system' to
distinguish Emacs running in a console/terminal from Emacs running with a window
mgr. In particular, I want to check whether Emacs supports keys such as S-TAB.

[Excuse me if console/terminal is not the right terminology, but I'm talking
about Emacs with no fancy keys such as S-TAB and less graphic support (colors,
fonts etc.) versus Emacs with no such limitations.]

`display-graphic-p' has apparently been with us since Emacs 22, but there is no
mention of it in the Elisp manual, even in Emacs 23. There is, however, plenty
of mention of `window-system', including node Window Systems.

Could someone please summarize the differences between the two, and when to use
one or the other? Please include how each might relate to use with a console,
-daemon, etc.

And could we then document this stuff in the manual? If it is in fact already
documented somewhere, then we can try to make it more visible or easier to find.

(FYI, I filed a bug about a general lack of clarity in the doc about terms
"graphical", "display", "terminal", and so on. But the bug site seems to be
down, so I don't know the bug #.)






       reply	other threads:[~2009-04-17 17:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m28wm31ock.fsf@nschum.de>
     [not found] ` <834owro4ha.fsf@gnu.org>
2009-04-17 17:37   ` Drew Adams [this message]
2009-04-17 18:15     ` how to use graphic-display-p and window-system Eli Zaretskii
2009-04-17 20:15       ` Drew Adams
2009-04-17 23:54         ` Stefan Monnier
2009-04-18  0:19           ` Drew Adams
2009-04-18  3:41             ` Stefan Monnier
2009-04-18  4:25               ` Drew Adams
2009-04-18  0:21           ` Miles Bader
2009-04-18  3:43             ` Stefan Monnier
2009-04-18  4:24               ` Drew Adams
2009-04-18  5:11               ` Miles Bader
2009-04-18  6:34           ` Eli Zaretskii
2009-04-18  7:01         ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001a01c9bf83$38bd2270$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).