Re: reftex-citation is not able to deal with several databases

[Colin Baxter]

> Uwe Brauer via Discussion list for AUCTeX developers 
>  writes:

> --=-=-= Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: quoted-printable

 "AE" =3D=3D Arash Esbati  writes:

>> Uwe Brauer via Discussion list for AUCTeX developers
>>  writes:
>>> Thanks for your answer. I found a solution that I posted, but it
>>> did not land in the same thread sorry.

>> Ah, Ok, I must have missed that, sorry.

>>> So the solution I found in=20
>>> 
https://bug-auctex.gnu.narkive.com/s2Oz8HpC/24-3-1-reftex-fails-to-find-=
> multiple-bib-files-in-bibliography-with-commas
>>> =20 I had to set (setq reftex-use-external-file-finders t) =20
>>> and everything worked as expected.

>> So you have your .bib files somewhere not next to your .tex file?
>> This was the case for me.


> My main bib file dwells in a (mercurial) repository somewhere on
> my disk, the other bib file I don't remember


>>> Maybe one should set this variable to t per default.

>> I don't think this is a good idea:

>> ,[ C-h v reftex-use-external-file-finders RET ] |
>> reftex-use-external-file-finders is a variable defined in
>> =E2=80=98reft=
> ex-vars.el=E2=80=99.
>> |=20 | Its value is nil |=20 | Non-nil means, use external
>> programs to find files.  | Normally, RefTeX searches the paths
>> given in the environment variables | TEXINPUTS and BIBINPUTS to
>> find TeX files and BibTeX database files.  | With this option
>> turned on, it calls an external program specified in t=
> he
>> | option =E2=80=98reftex-external-file-finders=E2=80=99 instead.
>> As a si=
> de effect,
>> | the variables
>> =E2=80=98reftex-texpath-environment-variables=E2=80=99 and |
>> =E2=80=98reftex-bibpath-environment-variables=E2=80=99 will be
>> ignored.  |=20 `

>> Changing the default of `reftex-use-external-file-finders' will
>> break for people who have set
>> `reftex-texpath-environment-variables' and/or
>> `reftex-bibpath-environment-variables'.

> Aha, I did not change the default behavior , |
> reftex-texpath-environment-variables is a variable defined in
> =E2=80=98re= ftex-vars.el=E2=80=99.  |=20 | Its value is
> ("TEXINPUTS") `

> , | reftex-bibpath-environment-variables is a variable defined
> in =E2=80=98re= ftex-vars.el=E2=80=99.  |=20 | Its value is
> ("BIBINPUTS" "TEXBIB") `

> But I see your point. Thanks

I have 10+ bibtex files in ~/texmf and my tex files elsewhere. I've
never had problems using reftex to find bib entries. I have
reftex-bibpath-environment-variables set to ("BIBINPUTS" "TEXBIB");
reftex-texpath-environment-variables set to ("TEXINPUTS") and
reftex-use-external-file-finders set to t.

I assume you are using reftex to find bib entries in auctex and not in
org-mode.

Best wishes,

Re: Supporting LatexMK in AUCTeX OOTB

[Colin Baxter]

>>>>> Arash Esbati  writes:

    > Colin Baxter  writes:
>> What is being proposed?

> See my other message to this thread.

>> This already works
>> 
>> (add-hook 'LaTeX-mode-hook (lambda() (add-to-list
>> 'TeX-command-list '("LaTeXMK" "latexmk %s" TeX-run-TeX nil t
>> :help "Run latexmk on master."

> Yes, but this is limited; AUCTeX provides some options to control
> the output and they are not respected in the above code.  If

I think I'll let my latexmkrc do the controlling. In any case, my
settings for latexmk don't change from document to document.

Best wishes,

Re: Supporting LatexMK in AUCTeX OOTB

[Colin Baxter]

>>>>> Ikumi Keita  writes:

> Hi Arash,
>>>>> Arash Esbati  writes:
>> Hi all, I was looking through our old bugs and I saw bug#48144[1]
>> which was about LatexMK and the issue is resolved.  Looking at
>> auctex-latexmk package[2], it seems dormant.  Acc. to this
>> message[3], the fix in #48144 was helpful and adding LatexMK
>> support to AUCTeX isn't hard.  I don't use LatexMK and don't have
>> any idea how it works, but adding two entries to
>> `TeX-expand-list' and `TeX-command-list' should be doable.

>> What do others think?  Is there a market for this addition?

> I'm fine with your idea. AUCTeX already has plenty of
> supplementary entries in `TeX-command-list', so it would be good
> to have another one :-)

> Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine #Gaza
> #StopMassiveKilling #CeasefireNOW

What is being proposed? This already works

(add-hook 'LaTeX-mode-hook
  (lambda()
(add-to-list
  'TeX-command-list
  '("LaTeXMK" "latexmk %s" TeX-run-TeX nil t
:help "Run latexmk on master."

Best wishes,

Colin Baxter.

Re: Annotating completion of labels

[Colin Baxter]

>>>>> Arash Esbati  writes:

    > Colin Baxter  writes:
>> When I insert a \label then what's in the bracket is always a
>> random alphanumeric, as in say \label{58f7161e}, and never some
>> descriptive text.

> Ok.

>> Obviously I refer to the label with \ref{58f7161e}. This is done
>> by hand; something which I don't find inconvenient because I
>> think it is more important for me to know where and what is
>> written in the text rather than ease of use.

> I'd suggest you start using RefTeX.  RefTeX can be configured to
> insert simple numbers after a prefix like 'eq:1' or 'sec:14'[1].
> Then you use C-) to reference a label and RefTeX starts a
> selection process incl. showing the text around the \label macro
> etc., very convenient.

Yes I know about this, but I prefer my method.


>> I envisaged that using your completion function would give me a
>> choice of random numbers.

> No, it gives you a list of already defined labels like 58f7161e
> incl. context (aka annotation).

>> Even if some run-on texts is included in the completion buffer
>> then this still might not provide sufficient context for me to
>> choose the completion accurately, especially if \label is some
>> distance away in the text from the corresponding \ref.

> My code relies solely on what RefTeX does: The text shown as
> annotation is what RefTeX holds in memory as context around the
> \label macro, and that can be configured.

>> All this might seem inconsistent with my supposed "knowing the
    >> text" and I may have completely misunderstood what you propose.

> I hope it is now more clear.

It is, thank you.

Best Wishes,

Colin Baxter.

Re: Annotating completion of labels

[Colin Baxter]

Dear Arash,

Thanks for your response
>>>>> Arash Esbati  writes:

    > Colin Baxter  writes:
>> Ok, I suppose for people who like that sort of this.

> Of course, the whole in-buffer completion thingy is for people who
> like it.

>> If implemented then I hope it would be off by default.

> The in-buffer completion machinery in AUCTeX is available by
> default, it kicks in once you use it.  It doesn't get in the way
> if you don't use it.  And in general, the related functions are
> designed to return quickly.  And file size doesn't really matter,
> other that during parsing.

>> I have many hundreds of labels in some TeX files and I would
>> worry that what you're proposing might slow down or hang my
>> emacs.

> If you're using RefTeX you shouldn't notice a difference.  My
> implementation uses `reftex-access-scan-info' which RefTeX does as
> well once used.

>> In any case, I generate random numbers to insert as labels, so
>> completion would be meaningless I think.

> Maybe I'm missing the point, but this is about referencing labels
> with \ref et al.  So why is completion meaningless inside a
> referencing macro?  I admit that RefTeX itself offers a much more
> powerful interface with `reftex-reference' bound to 'C-c )'

I think it might be me who's missing the point.

When I insert a \label then what's in the bracket is always a random
alphanumeric, as in say \label{58f7161e}, and never some descriptive
text. Obviously I refer to the label with \ref{58f7161e}. This is done
by hand; something which I don't find inconvenient because I think it is
more important for me to know where and what is written in the text
rather than ease of use.

I envisaged that using your completion function would give me a choice
of random numbers. Even if some run-on texts is included in the
completion buffer then this still might not provide sufficient context
for me to choose the completion accurately, especially if \label is some
distance away in the text from the corresponding \ref. All this might
seem inconsistent with my supposed "knowing the text" and I may have
completely misunderstood what you propose.

Best wishes,

Colin Baxter.

Re: Annotating completion of labels

[Colin Baxter]

>>>>> Arash Esbati  writes:

> Hi all, it occurred to me that we can teach AUCTeX to use RefTeX
> for annotating labels offered during in-buffer completion with
> some lines of code.  It can look like this:

> x


> What do people think?  Is this a useful feature?  Maybe we can do
> the same thing for cite commands.

Ok, I suppose for people who like that sort of this. If implemented then
I hope it would be off by default. I have many hundreds of labels in
some TeX files and I would worry that what you're proposing might slow
down or hang my emacs. In any case, I generate random numbers to insert
as labels, so completion would be meaningless I think.

Best wishes,

Colin Baxter.

Re: No syntax coloring in emacs-29.0.50

[Colin Baxter]

>>>>> Uwe Brauer  writes:

> --=-=-= Content-Type: text/plain Content-Transfer-Encoding:
> quoted-printable

>>>> "CB" =3D=3D Colin Baxter  writes:

>> The solution is to delete all the .elc files in the auctex
>> repository.

> I am confused,=20

> 1. Did you install auctex from the git repository or via the
> package s= ystem?

I use the auctex git repository -- I never ever use "packages". The "make"
command in the git directory byte-compiles the files. I add the git
directory to the load path and call auctex with the lines 

(setq load-path (cons "/path/to/git/auctex" load-path))
(load "/path/to/git/auctex/auctex.el" nil t t)

The setup has served me well over the years.

The problem may (or may not!) be related to recent issues with org-mode
and the latest emacs. There again, the solution is to delete the .elc
files. There is more about the latter on emacs-dev.

Best wishes,

Colin Baxter.

Re: No syntax coloring in emacs-29.0.50

[Colin Baxter]

The solution is to delete all the .elc files in the auctex repository.

Best wishes,

Colin Baxter.

Re: No syntax coloring in emacs-29.0.50

[Colin Baxter]

> Uwe Brauer  writes:

> This is why I said bisect is a bit lengthly to say the least, since
> you have to bisect  GNU emacs and not auctex.

I think I will leave this to others! :-)

Best wishes,

Colin.

No syntax coloring in emacs-29.0.50

[Colin Baxter]

Using the latest pulls from emacs-29.0.50 and auctex:

1. ~/git/emacs/src/emacs -q 
2. Open a tex file
3. Major mode is LaTeX and syntax coloring is present.
4. Kill tex file buffer
5. M-x clean-buffer-list 
6. eval (setq load-path (cons "/path/to/git/auctex" load-path))
7. eval (load "/path/to/git/auctex/auctex.el" nil t t)
8. Open the same tex used in (2) above
9. AucTeX is loaded and present in menu.
10. No syntax coloring is present.


The above does not happen with emacs-28.1

Best wishes,

Colin Baxter.

Re: Fontification of \include

[Colin Baxter ]

>>>>> Ikumi Keita  writes:

> Hi Arash,
>>>>> Arash Esbati  writes:
>> Hi all, I was wondering why \include is fontified like this:

> I wonder, too.

>> In font-latex.el, there is one entry for "include" in the
>> warning[1] and one in the reference keyword-class[2].

>> Is this what we want?  I suggest to remove the first entry and
>> fontify \include like \input.

>> Any comments welcome.

> I agree with your suggestion. Considering that \include and \input
> have similar functionality and similar syntax, it's natural to
> fontify them in the same way.

This is not true. \include cannot appear in the preamble since the
document has not started, but \include tells LaTeX to start new
pages. However \input can be used almost anywhere to insert
content, but \include must be by itself. The \input command can be
nested, but not \include, etc., etc. Please respect these differences.

Colin Baxter.

Re: Fontification of \include

[Colin Baxter ]

> Arash Esbati  writes:

> Is this what we want?  I suggest to remove the first entry and
> fontify \include like \input.

That's not a good idea. \include and \input are different and do
different things.

https://tex.stackexchange.com/questions/246/when-should-i-use-input-vs-include

https://latex.org/forum/viewtopic.php?t=11619

and others ...

Best wishes,

Re: On the usage and function of TeX-auto-generate-global and TeX-auto-global.

[Colin Baxter]

>>>>> Hongyi Zhao  writes:

> On Sun, Jul 4, 2021 at 9:42 PM Colin Baxter  wrote:
>> 
>> >>>>> Hongyi Zhao  writes:
    >> 
    >> > On Sun, Jul 4, 2021 at 9:19 PM Colin Baxter  wrote:
>> >>
>> >> Hello Hongyi
>> >>
>> >> I'm curious - what's your setting for the variable >>
>> "TeX-auto-local"?
>> 
>> > `M-x describe-variable RET TeX-auto-local RET'

Thanks - I didn't know that.

Best wishes,

Re: On the usage and function of TeX-auto-generate-global and TeX-auto-global.

[Colin Baxter]

>>>>> Hongyi Zhao  writes:

> On Sun, Jul 4, 2021 at 9:19 PM Colin Baxter  wrote:
>> 
>> Hello Hongyi
>> 
>> I'm curious - what's your setting for the variable
>> "TeX-auto-local"?

> `M-x describe-variable RET TeX-auto-local RET'

> TeX-auto-local is a variable defined in ‘tex.el’.

Thanks. I asked because I've set my TeX-auto-local to
~/.emacs.d/auctex/auto-local. It seems to be the only 'TeX-local'
variable that ever gets used. I have set TeX-auto-global to
~/.emacs.d/auctex/auto-global and it's always empty. I guess all the
work is being done by TeX-auto-local. I have certainly wondered when
Tex-auto-global is ever used.

Best wishes,

Colin.

Re: On the usage and function of TeX-auto-generate-global and TeX-auto-global.

[Colin Baxter]

Hello Hongyi

I'm curious - what's your setting for the variable "TeX-auto-local"?

Best wishes,

Colin Baxter.

Re: font-latex-match-warning-make void function.

[Colin Baxter]

> Tassilo Horn  writes:

> Stefan Monnier  writes:
>>> At last I managed to figure out the origin and seem to recover
>>> the normal behavior. Sorry for your inconvinience.
>> 
>> Clearly I'm to blame, so thanks for the fix.

> Get your shits together, Stefan, and thanks a lot! ;-)

> I've just merged master into externals/auctex.  Could you please
> check if everything's right there, i.e., foremost that changes in
> *.el.in files on master are in the corresponding *.el file in
> externals/auctex.

Things seem to be back to normal. Thanks to everyone.

Best wishes,

Re: font-latex-match-warning-make void function.

[Colin Baxter]

Dear Ikumi,

> Ikumi Keita  writes:
> Ah, no. The fontification doesn't happen when I open another latex
> file. I have to figure out why...

> Regards, Ikumi Keita

Yes, I can confirm that. I was too quick off the mark in my previous
email. I should have checked more thoroughly.

Best wishes,

Re: font-latex-match-warning-make void function.

[Colin Baxter]

>>>>> Ikumi Keita  writes:

> Hi Colin,
>>>>> Colin Baxter  writes:
>> After today's pull of auctex, I'm getting a
>> "font-latex-match-warning-make" void function error and auctex
>> will not load.

> Thank you, fixed in the git repo. Recent reorder in font-latex.el
> broke the dependency of function and variable.

> Regards, Ikumi Keita

Thank you, Ikumi. I can confirm that it is fixed.

Best wishes,

font-latex-match-warning-make void function.

[Colin Baxter]

Hello,

After today's pull of auctex, I'm getting a
"font-latex-match-warning-make" void function error and auctex will not
load.

Best wishes,

Colin Baxter.

Re: Loading AUCTeX out of Git repo

[Colin Baxter]

I think there's something wrong with commit f87d90f. I get a build doc
error:

install.texi:523: raising the section level of @subsubsection which is too low
Makefile:167: recipe for target '../INSTALL' failed
make[1]: *** [../INSTALL] Error 1
make[1]: Leaving directory '/home/redknight/git/auctex/doc'
Makefile:236: recipe for target 'docs' failed
make: *** [docs] Error 2

If I revert commit f87d90f74e6849cd3fc5f517c7dce8c58759573c then the
error disappears.

Best wishes,

Colin.

-- 
Colin Baxter
URL: http://www.Colin-Baxter.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-

Re: oddity with TeX-style-private ?

[Colin Baxter]

Hi Uwe,

>>>>> Uwe Brauer  writes:
> Ok but, do you also have the auctex ELPA package installed?  I
> have the feeling this makes the difference, and I will try out
> what Tassilo recommended.

No. I only use auctex from git. I had loads of trouble with stale and/or
mis-configured packages that I long ago stopped using them from ELPA and
MELPA. I now prefer instead to download the sources, usually from a git
depository, and manually install them.

Best wishes,

Colin.


Colin Baxter
URL: http://www.Colin-Baxter.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-

Re: oddity with TeX-style-private ?

[Colin Baxter]

Hello Tassilo,

>>>>> Tassilo Horn  writes:

> I also use the auctex master (or some other branch) checked out to
> ~/Repos/el/auctex/.  I just do

>   ./autogen.sh && ./configure --with-lispdir=. && make

> (i.e., I don't "make install") and use these auctex related
> configurations in my ~/.emacs.

> (setq TeX-data-directory "~/Repos/el/auctex" TeX-lisp-directory
> TeX-data-directory)

I have a similar arrangement to you, using auctex from git but without
actually installing. I do not however need to set explicitly the
TeX-data-directory - the variables TeX-data-directory and
TeX-lisp-directory automatically become
"/home//path/to/git/auctex/auctex".

I do set --prefix=/home//path/to/local/var/auctex in the Tex-style-path, which might
be useful one day.

Best wishes,

Colin Baxter.

 
Colin Baxter
URL: http://www.Colin-Baxter.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-

Re: oddity with TeX-style-private ?

[Colin Baxter]

On a related topic, the doc string for the variable 'TeX-auto-global'
says that it "must end with a directory separator". To me, a directory
separator is the oblique symbol '/' commonly called a
back-slash. However, the default setting for this variable, given in 
'tex-site.el' is "/usr/local/var/auctex", which does not end in '/'. 

It would seem I have not understood something here - but what?

Best wishes,

Colin Baxter.



Colin Baxter
URL: http://www.Colin-Baxter.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-
Since mathematicians have invaded the theory of relativity, I do not
understand it myself. A. Einstein

Re: TeX-master and TeX-output-master

[Colin Baxter]

; (let* ((mode-prefix (TeX-mode-prefix)) (suffixes (append
> (symbol-value (intern (concat mode-prefix
> "-clean-intermediate-suffixes"))) (when arg (symbol-value (intern
> (concat mode-prefix "-clean-output-suffixes")) (regexp (concat
> (mapconcat 'identity suffixes "\\|") "\\|" (regexp-quote
> (TeX-region-file t t) regexp))

> (define-advice TeX-active-master (:around (TeX-master-file-fn
>  extension  args) TeX-active-master-adv) (if (or
> (null extension) (equal extension t) (not (string-match-p
> (TeX-clean-extensions-regexp t) (concat "." extension (apply
> TeX-master-file-fn (cons extension args)) (TeX-master-output-file
> extension)))

> ;;; Example hook (defun set-latex-build-dir () ;; Check if
> the current file is its own master (setq TeX-output-dir "build/")
> (make-directory TeX-output-dir t) ;; Ensure directory exists (setq
> TeX-command-extra-options (concat TeX-command-extra-options "
> --output-directory=\"" TeX-output-dir "\"")))

> (add-hook 'LaTeX-mode-hook 'set-latex-build-dir)

I must say, this is very nice. I particularly like the comments in the
code --- refreshingly comprehensive and helpful in understanding
things. Option 1. above would seem the least drastic to me, and I'd
prefer it. I never use TeX-clean in order to avoid multiple+ runs each
time I compile.

All in all, I now think this will be a useful addition to auctex. Excellent.


Best wishes,

Colin.




-- 
Colin Baxter
URL: http://www.Colin-Baxter.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-

Re: TeX-master and TeX-output-master

[Colin Baxter]

Dear Tohiko
>>>>> Tohiko Looka  writes:

> Hello, I usually compile my latex files with pdflatex and use the
> argument `--output-directory` to have all output files saved
> inside a hidden `build` subdirectory (I also have a command to
> copy out the pdf output or attach it in an email... etc).  This
> clearly breaks auctex, because the master tex file is in a
> different directory from the required output files (log, aux and
> pdf).

> At the moment, I hacked together a solution by advising the
> function TeX-master-file to return a fake master which is inside
> my output directory. This works most of the time, but I did have
> to rewrite functions which require the correct path to the tex
> master file (like `TeX-synctex-output-page`).

> I was wondering if there's interest in extending auctex to have
> two properties: TeX-master and TeX-output-master. Then the correct
> master of the two is used in the hundred places or so in auctex
> where TeX-master-file is currently always used.

> -- Tohiko

Sorry Tohiko, but I for one do not see any advantage of further
complicating the procedure of using a master file. Such an addition
might be suitable for your workflow, but it wouldn't be for mine.

Would it not be prudent first to wait for input from other users in
order to gauge whether anyone else wants this addition?

Best wishes,

-- 
Colin Baxter
URL: http://www.Colin-Baxter.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-

Re: [AUCTeX-devel] Missing preview-latex.el

[Colin Baxter]

Thanks Tassilo, that fixed it. All is well.

Best wishes, Colin.

>>>>> Tassilo Horn  writes:

    > Colin Baxter  writes: Hi Colin,

>> In the latest git pull, I get a make error to the effect that
>> there's no preview-latex.el file. The file seems not to get
>> formed, or if it does then it's deleted in the compiling.

> Oh, there was a paren mismatch in style/amsmath.el which made make
> error out.  I've pushed a fix.

> Bye, Tassilo


> ___ auctex-devel
> mailing list auctex-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/auctex-devel

-- 
Colin Baxter
www.Colin-Baxter.com

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

[AUCTeX-devel] Missing preview-latex.el

[Colin Baxter]

In the latest git pull, I get a make error to the effect that there's no
preview-latex.el file. The file seems not to get formed, or if it does
then it's deleted in the compiling.

Nest wishes,


Colin Baxter.


___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] ChangeLog - recover previous behaviour.

[Colin Baxter]

Dear Arash,
>>>>> Arash Esbati  writes:

    > Colin Baxter  writes:
>> Apart from perhaps locally reverting 2a642a458, how do I recover
>> the old ChangeLog behaviour of not inserting a section heading
>> when I `C-x 4 a'?  I have tried (setq
>> add-log-current-defun-function nil) with no effect.

> Hi Colin,

> it doesn't work if you set a buffer-local variable on global
> level.  Put something like this in your .emacs:

> (defun reset-add-log-current-defun-function () (setq
> add-log-current-defun-function nil))

> (add-hook 'LaTeX-mode-hook #'reset-add-log-current-defun-function)

Thank you. That works!

Best wishes,

Colin Baxter
m43...@yandex.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

[AUCTeX-devel] ChangeLog - recover previous behaviour.

[Colin Baxter]

Apart from perhaps locally reverting 2a642a458, how do I recover the old
ChangeLog behaviour of not inserting a section heading when I `C-x 4 a'?
I have tried (setq add-log-current-defun-function nil) with no effect.

Best wishes,

Colin Baxter
m43...@yandex.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-


___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Many commands in TeX-command-list are not useful in context-mode

[Colin Baxter]

>>>>> Mohammad Hossein Bateni  writes:

> Please wait on this till I sort out the copyright.  On Sun, Apr
> 21, 2019 at 1:29 PM Mohammad Hossein Bateni 
> wrote:

>> Thanks for the review.
>> 
>> As noted by Mosè, this change does not affect latex-mode at all.
>> Its effect on context-mode is also minimal.  It basically allows
>> the user to pick and choose, while it removes a few tools from
>> the default for context-mode.
>> 
>> ConTeXt has two dialects now: Mark II and Mark IV.  BibTeX is
>> perhaps still used in Mark II, though I don't know how many
>> people actively use Mark II ConTeXt.  In Mark IV, I would say
>> BibTeX is not required.
>> 
>> Now I could be more aggressive and remove BibTeX from
>> context-mode in the default.  What do you think?
>> 
>> I will follow the instructions for assigning the copyright to
>> FSF.
>> 
>> On Sat, Apr 20, 2019 at 1:20 PM Colin Baxter  wrote:
>> 
>>> >>>>> Mosè Giordano  writes:
>>> 
>>> > Hi Colin, > On Fri, 19 Apr 2019 at 19:45, Colin Baxter
>>> 
>>> wrote:
>>> >> Not everybody uses ConTeXt and I for one use dvi2ps, ps2pdf
>>> and >> index nearly everyday.
    >>> 
>>> > Sure, but the proposed patch hides by default some commands in
>>> > context-mode only, LaTeX users won't be affected by this.
>>> 
>>> Thanks for the explanation.
>>> 
>>> Best wishes,
>>> 
>>> Colin Baxter m43...@yandex.com
>>> 
>> 


I think I was a little premature with the thanks. How do I get back to
the old behaviour of no section headings when I enter a changelog with
C-x 4a? I have tried

(setq add-log-current-defun-function nil)

with no effect. I still get an unwanted section heading.

Best wishes,

-- 
Colin Baxter
m43...@yandex.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Many commands in TeX-command-list are not useful in context-mode

[Colin Baxter]

>>>>> Mosè Giordano  writes:

> Hi Colin,
> On Fri, 19 Apr 2019 at 19:45, Colin Baxter  wrote:
>> Not everybody uses ConTeXt and I for one use dvi2ps, ps2pdf and
>> index nearly everyday.

> Sure, but the proposed patch hides by default some commands in
> context-mode only, LaTeX users won't be affected by this.

Thanks for the explanation.

Best wishes,

Colin Baxter
m43...@yandex.com

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Many commands in TeX-command-list are not useful in context-mode

[Colin Baxter]

 latex-mode doctex-mode ams-tex-mode texinfo-mode)
> + :help "Run makeglossaries to create glossary + file") + ("Index"
> "makeindex %s" TeX-run-index nil + (plain-tex-mode latex-mode
> doctex-mode ams-tex-mode texinfo-mode) :help "Run makeindex to
> create index file") - ("upMendex" "upmendex %s" TeX-run-index t t
    > + ("upMendex" "upmendex %s" TeX-run-index t + (plain-tex-mode
> latex-mode doctex-mode ams-tex-mode texinfo-mode) :help "Run
> upmendex to create index file") - ("Xindy" "texindy %s"
> TeX-run-command nil t + ("Xindy" "texindy %s" TeX-run-command nil
> + (plain-tex-mode latex-mode doctex-mode ams-tex-mode
> texinfo-mode) :help "Run xindy to create index file") ("Check"
> "lacheck %s" TeX-run-compile nil (latex-mode) :help "Check LaTeX
> file for correctness") -- 2.21.0


> ___ auctex-devel
> mailing list auctex-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/auctex-devel

Not everybody uses ConTeXt and I for one use dvi2ps, ps2pdf and index
nearly everyday.

Best wishes,

Colin Baxter
m43...@yandex.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-
Since mathematicians have invaded the theory of relativity, I do not
understand it myself. A. Einstein

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Setting `add-log-current-defun-function'

[Colin Baxter]

>>>>> Arash Esbati  writes:

> Uwe Brauer  writes:
>>>>> "AE" == Arash Esbati  writes:
>>> AUCTeX doesn't have a function to set
>>> `add-log-current-defun-function'.  Hence, hitting `C-x 4 a' in
>>> .tex file puts only the file name in the ChangeLog.  I suggest
>>> to add something like this to tex.el:
>> 
>> Very nice. I asked this question more than 10 years ago and
>> Carsten Dominik provided a small package which seems to do very
>> similar things to your code. At some point I asked to include the
>> code into auctex, but that was refused, but I don't recall the
>> reason.
>> 
>> I attach Carsten's code so that you can judge for yourself. I use
>> it very frequently and find it very useful.

> Hi Uwe,

> thanks for your response.  Nice piece of code, thanks for sharing
> it.  It does (more than less) what I've posted and since it relies
> on RefTeX, AUCTeX isn't the right place for it.  I'd like to hear
> if was rejected for any other reason back then.

How would your patch work when the ChangeLog is updated from a CVS log
using M-x vc-update-change-log ?

Best wishes,

-- 
Colin Baxter
m43...@yandex.com
-
The sole cause of all human misery is the inability of people to sit
quietly in their rooms.  Blaise Pascal, 1670

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Configure option --prefix seems broken partially (was Re: reftex-reference not including autoref)

[Colin Baxter]

>>>>> Colin Baxter  writes:


> ./configure --prefix=$HOME/local --with-texmf-dir=$HOME/texmf

Forgot the last line.

./configure --prefix=$HOME/local
--with-texmf-dir=$HOME/texmf
--with-emacs=$HOME/local/bin/emacs

Best wishes,

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Configure option --prefix seems broken partially (was Re: reftex-reference not including autoref)

[Colin Baxter]

> Ikumi Keita  writes:

> Hi all, I'm replying to a very old thread.  It seems that
> configure option --prefix is broken partially so that
> non-privileged users have difficulties at installing AUCTeX under
> home directory.

> Ikumi Keita  writes:
> Alex Branham  writes:
>>> I guess I'm doing something wrong when building it from git?
>>> Here's what I currently do:

>>> git clone https://git.savannah.gnu.org/git/auctex.git
>>> ~/.emacs.d/lib/auctex cd ~/.emacs.d/lib/auctex ./autogen.sh
>>> .configure --prefix=$HOME make

>> I guess that you didn't issue `make install' and
> ...(snip)...

> Actually I didn't try it by myself when I wrote this sentence.  I
> just recently realized that `make install' following the above
> procedure does not work as expected.

> After a similar procedure with env MAKE=gmake ./autogen.sh env
> MAKE=gmake ./configure --prefix=$HOME instead of `./autogen.sh'
> and `./configure --prefix=$HOME' because I have installed GNU make
> as gmake, my Makefile is:

> ...(snip)...  prefix = /home/keita$(null) exec_prefix =
> ${prefix}$(null) libdir = ${exec_prefix}/lib$(null) packagedatadir
> = /usr/local/share/emacs/site-lisp/auctex$(null) datarootdir =
> ${prefix}/share$(null) datadir = ${datarootdir}$(null)
> localstatedir = ${prefix}/var$(null) infodir =
> ${datarootdir}/info$(null) lispdir =
> /usr/local/share/emacs/site-lisp$(null)
> auctexstartfile=/usr/local/share/emacs/site-lisp/auctex.el
> previewstartfile =
> /usr/local/share/emacs/site-lisp/preview-latex.el packagelispdir =
> /usr/local/share/emacs/site-lisp/auctex$(null) packagedatadir =
> /usr/local/share/emacs/site-lisp/auctex$(null) packagedir =
> no$(null) autodir = ${localstatedir}/auctex$(null)
> preview_enabled=yes styledir = $(packagedatadir)/style
> ...(snip)...

> Note that there are several lines which assign absolute paths,
> overriding the --prefix option, to the make variables.  Thus lisp
> files don't go under the home directory but are rejected to
> install under "/usr/local/share/emacs/site-lisp" during `make
> install' without admin privilege.  This would be uncomfortable for
> users who try to install git development version under their home
> directories.

> I think this situation is not compatible with what is written in
> the section "Installation for non-privileged users" in INSTALL (or
> doc/install.texi).

> Shouln't `configure' (or `configure.ac'?) be rewritten to respect
> --prefix option for determining the install location of lisp
> files?  Or, alternaitively, is it the AUCTeX documents that should
> be revised?

> Regards, Ikumi Keita


./configure --prefix=$HOME/local --with-texmf-dir=$HOME/texmf

works for me.

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Typeset LaTeX files with non-ascii file name in TeXLive 2018

[Colin Baxter]

> Arash Esbati  writes:

> Ikumi Keita  writes:
>> The difference between my two patches are summarized below:
>> 1. Previous patch Good points: - LaTeX format version banner is
>> not discarded in the log file. [1] - First line parsing is not
>> disabled. [2] - Bug#25276 is fixed. [3] Bad points: - Users
>> cannot put TeX codes in a command line by default.  2. New patch
>> Good points: - Users still can put TeX codes in a command line.
>> Bad points: - LaTeX format version banner is discarded in the log
>> file by default.  - First line parsing is disabled by default.  -
>> Bug#25276 remains.
>> 
>> I still prefer the approach of the previous patch, but will honor
>> your opinion if you are still against it.

> Hi Keita,

> many thanks for working on this.  I haven't looked at the patch,
> but I think we should keep `TeX-command-extra-options' working.
> It is a very flexible way to control the binary invoked on a file
> basis.  E.g., all files which \usepackage{minted} need this:

> %%% TeX-command-extra-options: "-shell-escape"

> I'm not sure if first line parsing is so important.  The issue
> described here[1] can be solved with

> %%% TeX-command-extra-options: "--fmt=foo.fmt"

> Hence, I'm voting to keep this feature running and drop something
> else.

I agree.

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Typeset LaTeX files with non-ascii file name in TeXLive 2018

[Colin Baxter]

> Ikumi Keita  writes:

> Hi developpers, I'd like to commit a change proposed in
> https://lists.gnu.org/archive/html/auctex/2018-05/msg00014.html in
> order to resolve problems addressed in
> https://lists.gnu.org/archive/html/auctex/2018-05/msg3.html
> https://lists.gnu.org/archive/html/auctex/2018-05/msg4.html .
> Are there anyone who doesn't agree with this?

> As explained in ealier messages, this patch introduces some
> incompatibilities: - Users cannot put raw TeX codes in the command
> line like latex -interaction=nonstopmode \SOME_CODE \input
> FILENAME via setting `TeX-command-extra-options' anymore, as long
> as the default `TeX-command-list' is used.  - (Pdf)latex binaries
> without e-TeX extension have the following two limitations:
> 1. Preview-latex does not work.  (This can be circumvented by
> customizing `preview-LaTeX-command' and
> `preview-undump-replacements' to cancel the change by my patch,
> though) 2. Region compilation (C-c C-r, C-c C-e etc.) does not
> work.  I.e., such binaries can only use C-c C-c (and C-c C-a) to
> typeset the latex documents.  If you consider that these
> incompatibilities are not acceptable, please express your opinion.
> I would be ready to discuss about this.

> If no objection, I'll commit the change in a few days.  Adding
> document changes and regression tests will follow later.

> Best regards, Ikumi Keita

> P.S.  I tested the patch with MikTeX briefly, and encountered no
> errors.


I really do not like what I understand to be this suggestion. If users
cannot put TeX codes in a command then extensive functionality is
lost. The bar on non-ascii file names seems trivial to me - sorry.

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] What is the proper way to install auctex as a user?

[Colin Baxter]

> Arash Esbati  writes:

> Alex Branham  writes:
>> I'm running into some font-lock issues that I didn't have before
>> switching over to building auctex from the git repo. I'm
>> wondering how I'm supposed to build and activate auctex. I clone
>> auctex to ~/.emacs.d/lib/auctex and then do the following:
>> 
>> ./autogen.sh ./configure --prefix=$HOME make

> Hi Alex,

> I do basically the same thing, but issue a `make extraclean'
> before `./autogen.sh'.  Do you want to give it a roll?

Would `make distclean' have the same effect?

Best wishes

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] support for xemacs

[Colin Baxter]

>>>>> Mosè Giordano <m...@gnu.org> writes:

> Hi all, I'm resurrecting this thread to raise again the question:

>   Is there anyone with strong arguments against dropping support
> in AUCTeX for all Emacsen whose version is < 24 (thus including
> all versions of XEmacs)?

> Keep in mind that supporting old platforms requires time, so in
> case you wish to keep support for them it would be great if you
> volunteer doing so :-)

> Cheers, Mosè

> ___ auctex-devel
> mailing list auctex-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/auctex-devel

You might want to follow org-mode and drop supporting xemacs. According
to ORG-NEWS, support for xemacs was dropped at org-version 9.0


Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8


___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

[Colin Baxter]

>>>>> gojjoe  <goj...@gmail.com> writes:

> It's code but also and foremost a typographic tool. When finishing
> to latex-typeset a document – and "finishing" can take quite some
> time in itself – I think it's inevitable to alternately compile
> and check the output continuously, to see if some parts of text
> look better in a certain disposition or another, or to find the
> best position for that important figure. Especially if you know
> the text will be printed. Not even auctex's preview can help for
> this; its purpose is different. I'm sure this is the case for most
> latex users, or for many of them at least.


I'm sure you're right. As an old timer (TeX since 1980s) I'm probably
stuck in my ways :-(.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

[Colin Baxter]

>>>>> "David" == David Kastrup <d...@gnu.org> writes:

David> Colin Baxter <m43...@yandex.com> writes:
>>>>>>> "Tassilo" == Tassilo Horn <t...@gnu.org> writes:
>> 
Tassilo> Mosè Giordano <m...@gnu.org> writes: Hi!
>> 
>> >>> Do you all agree to make this an option? If so, I can update
>> the >>> patch to accommodate that.  >> >> I'm not still convinced
>> that the patch you propose is a good >> idea.  Why should people
>> run "View" command to *not* view the >> document?
>> 
Tassilo> I know what Hong's referring to.  You want to view the
Tassilo> document in Evince but keep editing in emacs, thus the
Tassilo> input focus should stick there.
>> 
>> To me, and assuming I have not totally misunderstood the
>> proposal, there seems to be a philosophical issue here. If you
>> were to write a program, you wouldn't expect to view the output
>> of the compilation as you enter the code. You might look at an
>> initial output but then you would concentrate on the code before
>> compiling again - you surely wouldn't do both
>> simultaneously. TeX/LaTeX is also code, so why would not the same
>> expectation apply? I apologise if I have misunderstood.

David> Well, your philosophy did not manage to prevent
David> preview-latex.

Very true. I can only claim never to have used it.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

[Colin Baxter]

>>>>> "Tassilo" == Tassilo Horn <t...@gnu.org> writes:

Tassilo> Mosè Giordano <m...@gnu.org> writes: Hi!

>>> Do you all agree to make this an option? If so, I can update the
>>> patch to accommodate that.
>> 
>> I'm not still convinced that the patch you propose is a good
>> idea.  Why should people run "View" command to *not* view the
>> document?

Tassilo> I know what Hong's referring to.  You want to view the
Tassilo> document in Evince but keep editing in emacs, thus the
Tassilo> input focus should stick there.

To me, and assuming I have not totally misunderstood the proposal, there
seems to be a philosophical issue here. If you were to write a program,
you wouldn't expect to view the output of the compilation as you
enter the code. You might look at an initial output but then you would
concentrate on the code before compiling again - you surely wouldn't do
both simultaneously. TeX/LaTeX is also code, so why would not the same
expectation apply? I apologise if I have misunderstood.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

[Colin Baxter]

>>>>> "Hong" == Hong Xu <h...@topbug.net> writes:

    Hong> On 08/09/2017 11:46 PM, Colin Baxter wrote:
>> Dear Hong,
>>>>>>> "Hong" == Hong Xu <h...@topbug.net> writes:
>> 
Hong> On 08/09/2017 07:37 PM, Mosè Giordano wrote:
>> >> Hi!  >> >> 2017-08-09 11:21 GMT+02:00 Hong Xu
>> <h...@topbug.net>: >>> The current behavior switches focus to
>> Evince, which is >>> inconvenient for editing.  >> >> I guess
>> you're referring to this: >>
>> https://emacs.stackexchange.com/q/34754/620 `C-c C-v' is used to
>> >> open the viewer, so why you would like to keep focus on Emacs
>> if >> you request to open the viewer?  If you want to keep focus
>> on >> Emacs, do not open the viewer.  Or am I missing something?
>> >>
>> 
Hong> When syncing, I would like to see how what I've just typed is
Hong> shown in the produced PDF file. For that matter, I still would
Hong> like to continue editing, but switching focus interrupts the
Hong> flow. At least, I think, there should be an option to change
Hong> this behavior.
>> 
>> 
>> 'C-c C-v' doesn't only work for evince but other viewers,
    >> e.g. xdvi. So if it's changed for evince, it will be changed for
>> non-evince users too.
>> 

Hong> Certainly. This can be an option for all evince based viewers.

I never use evince so I don't have an opinion to an evince-only option.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] [PATCH] When using SyncTeX with Evince, do not switch focus after syncing.

[Colin Baxter]

Dear Hong,
>>>>> "Hong" == Hong Xu <h...@topbug.net> writes:

Hong> On 08/09/2017 07:37 PM, Mosè Giordano wrote:
>> Hi!
>> 
>> 2017-08-09 11:21 GMT+02:00 Hong Xu <h...@topbug.net>:
>>> The current behavior switches focus to Evince, which is
>>> inconvenient for editing.
>> 
>> I guess you're referring to this:
>> https://emacs.stackexchange.com/q/34754/620 `C-c C-v' is used to
>> open the viewer, so why you would like to keep focus on Emacs if
>> you request to open the viewer?  If you want to keep focus on
>> Emacs, do not open the viewer.  Or am I missing something?
>> 

Hong> When syncing, I would like to see how what I've just typed is
Hong> shown in the produced PDF file. For that matter, I still would
Hong> like to continue editing, but switching focus interrupts the
Hong> flow. At least, I think, there should be an option to change
Hong> this behavior.


'C-c C-v' doesn't only work for evince but other viewers, e.g. xdvi. So
if it's changed for evince, it will be changed for non-evince users too.

Best wishes,

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] AUCTeX without Desktop Environment

[Colin Baxter]

Dear Uwe,

>>>>> "Uwe" == Uwe Brauer <o...@mat.ucm.es> writes:

Uwe> Hello


>> Hello Easior,


>> This is probably not what you want to hear but I'm tempted to
>> suggest you dump evince, which, in my opinion, is bloated. Auctex
>> and xpdf work happily without a graphical user interface. I use
>> them in xmonad.

Uwe> Interesting, I like xpdf because it is lightweight, but how do
Uwe> you manage inverse and forward search in your pdf files with
Uwe> xpdf?

I don't. I just grep the source files.

Uwe> I switched from xpdf to okular (which is recently quite buggy)
Uwe> and then to evince which is not as fast as xpdf but supports
Uwe> both searches.

Yes, I tried okular but found it often hung - or crashed! Xpdf is old, I
know, but it works.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] AUCTeX without Desktop Environment

[Colin Baxter]

Hello Easior,
>>>>> Easior Lars <eas...@126.com> writes:

> Thank you, Colin.

>>>>> "CB" == Colin Baxter <m43...@yandex.com> writes:
CB> This is probably not what you want to hear but I'm tempted to
CB> suggest you dump evince, which, in my opinion, is
CB> bloated. Auctex and xpdf work happily without a graphical user
CB> interface. I use them in xmonad.

> Maybe, it is a good idea to use xpdf in Qtile. Can you share an
> AUCTeX configuration about xpdf to me? It's better if AUCTeX can
> automatically tell itself in GNOME DE or not.

I have attached my auctex settings, and also a small org-mode setting
for use in exporting to pdf (which you may not want, of course).



my-autec.el
Description: application/emacs-lisp


my-pdf-org.el
Description: application/emacs-lisp

You probably don't need this, but I have the following in my ~/.mailcap

application/pdf; xpdf %s
application/postscript; gv %s
application/x-dvi; xdvi %s

Best wishes.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] AUCTeX without Desktop Environment

[Colin Baxter]

Hello Easior,

>>>>> Easior Lars <eas...@126.com> writes:

> while any LaTeX source file opened in Emacs. I have no idea about
> how to resolve it. Is it possible to let AUCTeX without desktop
> environment work? Any hint?

This is probably not what you want to hear but I'm tempted to suggest
you dump evince, which, in my opinion, is bloated. Auctex and xpdf work
happily without a graphical user interface. I use them in xmonad.

Best wishes,

Colin.

-- 
--
Colin Baxter
m43...@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Defaulting `TeX-parse-self' to t

[Colin Baxter]

On Sun, Feb 05 2017, Uwe Brauer wrote:

 "Arash" == Arash Esbati  writes:
>
>> Hi all,
>> is there a particular reason why AUCTeX sets `TeX-parse-self' to nil?
>> Does this reason still apply or can we default it to t?
>
>
>> I have the impression that this decision is leading to a new standard
>> answer which is "customize latex-verbatim-environments or
>> latex-verbatim-environments-local" when somebody asks for "How do I add
>> my defined verbatim env to AUCTeX?"  We have many style files and they
>> are in a good shape; I think we should move users in a direction that
>> they actually use them and get all the benefits.
>
> I am all for it. This variable should be t (per default)
>
> Uwe

You may be. For every 100 users who want Y you'll be able to find
another 100 who do not. The whole point of a default is that it's just
that - default. Leave defaults alone but make sure all options to
the default are well documented, which they are in this case.

Best -

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel

Re: [AUCTeX-devel] Defaulting `TeX-parse-self' to t

[Colin Baxter]

On Sat, Feb 04 2017, Arash Esbati wrote:

> Hi all,
>
> is there a particular reason why AUCTeX sets `TeX-parse-self' to nil?
> Does this reason still apply or can we default it to t?
>
> I have the impression that this decision is leading to a new standard
> answer which is "customize latex-verbatim-environments or
> latex-verbatim-environments-local" when somebody asks for "How do I add
> my defined verbatim env to AUCTeX?"  We have many style files and they
> are in a good shape; I think we should move users in a direction that
> they actually use them and get all the benefits.
>
> WDYT?
>
> Best, Arash

Please do not change defaults. There is nothing to stop users setting
putting (setq TeX-parse-self t) if they wish.

___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel