all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Drew Adams <drew.adams@oracle.com>
Cc: 'Sebastien Vauban' <wxhgmqzgwmuf@spammotel.com>, help-gnu-emacs@gnu.org
Subject: Re: Using the same custom file in two different OSes
Date: Thu, 17 Jan 2013 15:38:32 +0100	[thread overview]
Message-ID: <4A918D61-83A2-4C60-A35C-9EA5CCF24090@Web.DE> (raw)
In-Reply-To: <D3691C5E9E284C6D952B1AF46070CAE7@us.oracle.com>


Am 17.01.2013 um 15:19 schrieb Drew Adams:

>>>  (if (display-graphic-p) ...
>> 
>> FYI, I'm using: (if window-system ...
>> but that comes down to pretty much the same thing, it seems.
> 
> `window-system' has the advantage that it works with older Emacs releases.
> 
> But `display-graphic-p' is what is recommended for recent releases.
> From the doc string of `window-system':
> 
> "Use of this function as a predicate is deprecated.  Instead,
>  use `display-graphic-p' or any of the other `display-*-p'
>  predicates which report frame's specific UI-related capabilities."
> 
> 
This looks more like a regression than progress…

The variable `window-system' at least returns a value indicating on which kind of graphic display this instance of GNU Emacs runs: x, w32, ns, pc, mac. These variants still need different set-ups. And it also makes sense to decorate the instance running in different colours to see at once in which variant I'm in.

In future one might need to parse the text returned by `emacs-version' to find this information – and might fail at first because being build for a graphic display does not exclude its use without a windowing system. So one would need a second test.

--
Greetings

  Pete

Eat the rich – the poor are tough and stringy.




  reply	other threads:[~2013-01-17 14:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13 22:00 Using the same custom file in two different OSes Dani Moncayo
2013-01-13 22:18 ` Drew Adams
2013-01-14 18:46   ` Dani Moncayo
2013-01-14 19:13     ` Drew Adams
2013-01-14 19:42       ` Dani Moncayo
2013-01-14 21:55         ` Peter Dyballa
2013-01-14 23:00           ` Dani Moncayo
2013-01-15  8:25             ` Didier Verna
2013-01-15  8:42               ` Dani Moncayo
2013-01-14 22:05         ` Drew Adams
2013-01-16 21:03           ` Dani Moncayo
     [not found]           ` <mailman.17633.1358371586.855.help-gnu-emacs@gnu.org>
2013-01-17  8:43             ` Sebastien Vauban
2013-01-17 14:19               ` Drew Adams
2013-01-17 14:38                 ` Peter Dyballa [this message]
2013-01-17 15:22                   ` Dani Moncayo
2013-01-17 16:38                     ` Eli Zaretskii
2013-01-17 16:01                   ` Drew Adams
2013-01-17 16:33                   ` Eli Zaretskii
2013-01-17 16:32                 ` Eli Zaretskii
2013-01-17 16:57                   ` Drew Adams
2013-01-17 17:48                     ` Eli Zaretskii
2013-01-17 18:15                       ` Drew Adams
2013-01-17 18:44                         ` Eli Zaretskii
2013-01-15 13:27 ` Stefan Monnier
2013-01-15 20:27   ` Dani Moncayo
     [not found]   ` <mailman.17532.1358281671.855.help-gnu-emacs@gnu.org>
2013-01-16  8:58     ` Sebastien Vauban
2013-01-16 20:35       ` Dani Moncayo
2013-01-16 12:59     ` Jason Rumney

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=4A918D61-83A2-4C60-A35C-9EA5CCF24090@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.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.