From: Ralf Angeli <dev.null@caeruleus.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Changing default dvi viewer.
Date: Sat, 09 Feb 2008 11:03:26 +0100 [thread overview]
Message-ID: <47ad7a6e$0$4284$9b4e6d93@newsspool3.arcor-online.net> (raw)
In-Reply-To: mailman.7202.1202549941.18990.help-gnu-emacs@gnu.org
* Peter Dyballa (2008-02-09) writes:
> Am 08.02.2008 um 21:18 schrieb Ralf Angeli:
>
>> This is a very bad idea since you will have to check if something
>> changed in texdoc every time the TeX distribution is updated unless
>> you
>> don't mind missing new features and bug fixes or dealing with
>> potential
>> incompatibilities.
>
> This isn't such a big issue. TeX Live updates happen once in two
> years, before 2006 it was once per year.
What you are suggesting is just plain unnecessary because there are
other ways of achieving the goal of abusing `texdoc' as a replacement
for `run-mailcap' (aka `see'), namely setting the environment variables
used by `texdoc' or adapting the mailcap configuration. Please, inform
yourself before making suggestions.
>> In addition you lose the capability of passing the paper size to the
>> viewer. So this is an exceptionally bad suggestion for the case at
>> hand
>> where a DVI viewer is being dealt with.
>
> The latter is true, and I did not emphasise enough that David should
> only change one xdvi entry with texdoc (it is so obvious to me), the
> one that uses his default paper size.
And how would that help? Then he still gets `xdvi' for the other cases.
Just do `M-x customize-variable <RET> TeX-output-view-style <RET>',
search for instances of "xdvi" and replace them with "kdvi", assuming
`kdvi' takes the same command line options as `xdvi'. Big deal!
--
Ralf
next prev parent reply other threads:[~2008-02-09 10:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080205170541.675151BC01F@ufc.univ-fcomte.fr>
2008-02-07 11:28 ` Changing default dvi viewer David
2008-02-07 10:51 ` Peter Dyballa
2008-02-07 15:30 ` David
2008-02-07 15:00 ` Peter Dyballa
2008-02-07 16:26 ` David
2008-02-07 18:32 ` Peter Dyballa
2008-02-08 13:39 ` David
2008-02-08 13:50 ` Peter Dyballa
2008-02-08 14:09 ` David
2008-02-08 14:52 ` Peter Dyballa
2008-02-08 14:11 ` Thierry Volpiatto
2008-02-08 14:15 ` David
2008-02-08 14:50 ` David
2008-02-08 15:37 ` Peter Dyballa
2008-02-08 17:07 ` David
2008-02-08 14:20 ` Thierry Volpiatto
2008-02-08 14:21 ` David
2008-02-08 15:07 ` Thierry Volpiatto
[not found] ` <mailman.7120.1202409178.18990.help-gnu-emacs@gnu.org>
2008-02-08 20:18 ` Ralf Angeli
2008-02-09 9:38 ` Peter Dyballa
[not found] ` <mailman.7202.1202549941.18990.help-gnu-emacs@gnu.org>
2008-02-09 10:03 ` Ralf Angeli [this message]
2008-02-07 10:56 ` Tassilo Horn
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='47ad7a6e$0$4284$9b4e6d93@newsspool3.arcor-online.net' \
--to=dev.null@caeruleus.net \
--cc=angeli@caeruleus.net \
--cc=help-gnu-emacs@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.
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).