From: Tariq <tariq.perwez@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: xelatex menu option does not show
Date: Tue, 27 Apr 2010 11:22:23 -0700 (PDT) [thread overview]
Message-ID: <91f88420-24d1-45d5-bbbc-9a745953e851@x5g2000vbf.googlegroups.com> (raw)
In-Reply-To: 87och4n5d8.fsf@fh-trier.de
On Apr 27, 1:59 pm, Andreas Politz <poli...@fh-trier.de> wrote:
> Tariq <tariq.per...@gmail.com> writes:
> > I must add to the above the following observation. With the above code
> > in my .emacs file, if I open a XeLaTeX file and compile once using the
> > XeLaTeX option in the Command menu (i.e. using mouse) and then for the
> > subsequent compilations, C-c C-c does give me
>
> > Command: (default XeLaTeX)
>
> > in the minibuffer. Otherwise, if I just open a XeLaTeX file and press
> > C-c C-c all I get is
>
> > Command: (default LaTeX)
>
> > in the minibuffer.
>
> > This is not a desirable behaviour at all. I should be able to get
> > Command: (default XeLaTeX) the very first time I press C-c C-c if the
> > file I have is XeLaTeX file!
>
> > How can I correct this? Best regards,
>
> > Tariq
>
> Maybe the criteria for what constitutes a XeLaTeX file in your head, is
> different from what your code specifies. In other words, the regexp is
> not able to match and thus, "LaTeX" becomes the default command.
>
> -ap
Hi Andreas
Perhaps so, but I thought the code specified that the presence of the
fontspec package should constitute the file being a XeLaTeX file and
hence C-c C-c should result in XeLaTeX as the default engine. Is this
not right? The mouse click does work. And, after one compilation with
mouse click, C-c C-c also works. Puzzling.
Or, can some change be made to the code to make it work as I want?
Regards,
Tariq
prev parent reply other threads:[~2010-04-27 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 19:03 xelatex menu option does not show Tariq
2010-04-26 20:45 ` Andreas Politz
2010-04-27 1:58 ` Tariq
2010-04-27 15:49 ` Tariq
2010-04-27 16:08 ` Tariq
2010-04-27 17:59 ` Andreas Politz
2010-04-27 18:22 ` Tariq [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=91f88420-24d1-45d5-bbbc-9a745953e851@x5g2000vbf.googlegroups.com \
--to=tariq.perwez@gmail.com \
--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).