unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ralf Angeli <angeli@caeruleus.net>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Custom themes and simple variables
Date: Fri, 23 Oct 2009 19:55:01 +0200	[thread overview]
Message-ID: <87aaziov0q.fsf@caeruleus.net> (raw)
In-Reply-To: <873a5arp1g.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 23 Oct 2009 13:35:55 -0400")

* Chong Yidong (2009-10-23) writes:

> Ralf Angeli <angeli@caeruleus.net> writes:
>
>> The idea now is that the list of predefined viewers only contains
>> viewers for the chosen platform.  Per default viewers available on
>> GNU/Linux would be offered but if a theme for MiKTeX on Windows were
>> enabled, only viewers available on Windows would be displayed.
>
> Why not automatically detect the system type in the initialization form
> for either the defvar'ed list of built-in viewers, or the defcustom
> default for the user viewer?  I.e., either
>
> (defvar available-viewers (cond (eq system-type 'gnu/linux) ....))
>
> or
>
> (defcustom my-viewer (cond (eq system-type 'gnu/linux) ....))
>
> depending on whichever makes more sense for the particular situation.

The operating system is not the only condition influencing the list of
viewers (and at least one additional internal variable).  Another
important one is the TeX system in use.  And I could imagine that there
are even people with multiple TeX systems installed who'd like to be
able to switch between them.  Custom themes would make that quite
convenient.

Currently something like this is used in the files users can require to
activate platform-specific settings:

(unless (get 'TeX-kpathsea-path-delimiter 'saved-value)
  (setq TeX-kpathsea-path-delimiter nil))

It's working but it's a bit less convenient.

-- 
Ralf




      reply	other threads:[~2009-10-23 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 21:11 Custom themes and simple variables Ralf Angeli
2009-10-23 16:53 ` Chong Yidong
2009-10-23 17:05   ` Ralf Angeli
2009-10-23 17:35     ` Chong Yidong
2009-10-23 17:55       ` Ralf Angeli [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

  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=87aaziov0q.fsf@caeruleus.net \
    --to=angeli@caeruleus.net \
    --cc=cyd@stupidchicken.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).