unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
Cc: steve@doodlebeth.com, emacs-devel@gnu.org
Subject: Re: TeX called improperly
Date: Sat, 20 Apr 2002 13:42:36 -0400	[thread overview]
Message-ID: <200204201742.g3KHgal10077@f7.net> (raw)

    What do you think is the right solution, the right way to handle
    tex-start-options-string?

To expand a little ...

Looking at the original bug report again, I see the problem was the
quotes, right?  So Emacs should strip off the quotes before sending it
to tex, so the multiple options come through as multiple options.

I'm surprised that this does not happen at a lower level actually, since
I thought all those quotes mean is that the Local Variables: value is a
string constant.

Perhaps Emacs is adding its own quotes back to the command, so that the
local var could be set to a value like "\\nonstopmode\\input foo" and
this would get passed on the command line as '\nonstopmode\input foo'.

Unfortunately that won't work in the presence of multiple options, so
all I can suggest is for Emacs not to be so smart, and just pass the
value it is given.  It'll have to be up to the user to put in the right
number of backslashes (four, I guess).

Or if there is too problematic for compatibility, I guess another
variable could be introduced.  (tex-start-options-no-implicit-quoting)

Hope this helps,
k

             reply	other threads:[~2002-04-20 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20 17:42 Karl Berry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-20 17:34 TeX called improperly Karl Berry
2002-04-22  7:46 ` Richard Stallman
2002-04-19 20:01 Karl Berry
2002-04-20 17:27 ` Richard Stallman
     [not found] <auto-000037014791@dc-mx05.cluster1.charter.net>
     [not found] ` <200204162017.g3GKHwc24346@aztec.santafe.edu>
     [not found]   ` <auto-000001251224@mx06.cluster1.charter.net>
2002-04-19 18:43     ` Richard Stallman

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=200204201742.g3KHgal10077@f7.net \
    --to=karl@freefriends.org \
    --cc=emacs-devel@gnu.org \
    --cc=steve@doodlebeth.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 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).