bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-02 Thread Tassilo Horn
Ikumi Keita writes: Hi Ikumi, >> Did you also check that the feature works? That is, that the code >> between | and | in > >> \mycode|(lambda () "wohoo")| > >> is highlighted as verbatim in a file with > >> %% Local Variables: >> %% LaTeX-verbatim-macros-with-delims:

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-02 Thread Ikumi Keita
Hi Tassilo, > Did you also check that the feature works? That is, that the code > between | and | in > \mycode|(lambda () "wohoo")| > is highlighted as verbatim in a file with > %% Local Variables: > %% LaTeX-verbatim-macros-with-delims: ("mycode") > %% End: I checked with the given example.

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-02 Thread Ikumi Keita
Hi Tassilo, > Ikumi, I'll implement that now. Could you please check if it works as > expected in the coming days? With the updated code, the error went away. Thank you. Bye, Ikumi Keita ___ bug-auctex mailing list bug-auctex@gnu.org

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-01 Thread Tassilo Horn
Thank you. My job here is almost done, too. ;-) Am 1. Februar 2017 20:42:54 schrieb Mosè Giordano : 2017-02-01 11:20 GMT-08:00 Tassilo Horn : Gosh, can you please clean up after me? I'm already in the bringing sick son to bed business which might take a while.

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-01 Thread Mosè Giordano
2017-02-01 11:20 GMT-08:00 Tassilo Horn : > Gosh, can you please clean up after me? I'm already in the bringing sick son > to bed business which might take a while. Done. Bye, Mosè ___ bug-auctex mailing list bug-auctex@gnu.org

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-01 Thread Tassilo Horn
Gosh, can you please clean up after me? I'm already in the bringing sick son to bed business which might take a while. If not, no problem, I'll fix it tomorrow. Bye, Tassilo Am 1. Februar 2017 19:57:12 schrieb Mosè Giordano : 2017-02-01 10:29 GMT-08:00 Tassilo Horn

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-01 Thread Mosè Giordano
2017-02-01 10:29 GMT-08:00 Tassilo Horn : > Tassilo Horn writes: > >> Ikumi, I'll implement that now. Could you please check if it works as >> expected in the coming days? > > Pushed with commit d54e7472. The second argument of `local-variable-p' is mandatory in

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-01 Thread Tassilo Horn
Tassilo Horn writes: > Ikumi, I'll implement that now. Could you please check if it works as > expected in the coming days? Pushed with commit d54e7472. Bye, Tassilo ___ bug-auctex mailing list bug-auctex@gnu.org

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-01 Thread Mosè Giordano
Hi Tassilo, 2017-02-01 7:57 GMT+01:00 Tassilo Horn : > Do you know if XEmacs has some similar feature, i.e., a way to check > which variables have been set using file (or directory) local variables? If you want to check whether a variable was set locally in a XEmacs-compatible way

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-02-01 Thread Ikumi Keita
Hi Tassilo, > Do you know if XEmacs has some similar feature, i.e., a way to check > which variables have been set using file (or directory) local variables? Hmm, now I'm looking at files.el of xemacs and unfortunately xemacs doesn't seem to have such features. Bye, Ikumi Keita

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-01-31 Thread Tassilo Horn
Ikumi Keita writes: Hi Ikumi, > Opening circ.tex with xemacs leads to the following error: > -- > (1) (local-variables/warning) File local-variables error: Symbol's value as > variable is void:

bug#25564: 11.90; XEmacs lacks file-local-variables-alist and reports error.

2017-01-28 Thread Ikumi Keita
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. Be sure to consult the FAQ section in the manual before submitting a bug report. In addition check if the bug is reproducable with an up-to-date version of AUCTeX. So please upgrade to the version