Re: [AUCTeX] AUCTeX has a logo!

Great! Thank you very much for the logo and AUCTeX! - ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial

[AUCTeX-commit] GNU AUCTeX branch, master, updated. 46059c345bdc6cfad9de3987bee5e609e670fc61

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU AUCTeX". The branch, master has been updated via 46059c345bdc6cfad9de3987bee5e609e670fc61 (commit) from

[AUCTeX-diffs] GNU AUCTeX branch, master, updated. 46059c345bdc6cfad9de3987bee5e609e670fc61

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU AUCTeX". The branch, master has been updated via 46059c345bdc6cfad9de3987bee5e609e670fc61 (commit) from

Re: [AUCTeX-devel] Automatic adding of label to optional argument

Hi Arash, 2017-01-12 18:35 GMT+01:00 Arash Esbati : > Hi all, > > some packages like listings.sty have a label key since one cannot put > \label in the body of the environment. I wrote a function which uses > the standard interface of AUCTeX and/or RefTeX for inserting a \label >

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

Le 12/01/2017 à 20:40, Mosè Giordano a écrit : 2017-01-12 20:08 GMT+01:00 jfbu : I get the script raising to work fine, but under the condition of typing explicitely braces, i.e. \( x^{y^{z^a_b}} \) does the expected thing from the docs after having set to multi-level the

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

Le 12/01/2017 à 21:43, jfbu a écrit : (some problem we discussed here months ago, which I have forgotten now) the problem was about use in .dtx file which will never have empty line in the implementation section due to % prefix. in my dtx, the documentation section has no % prefix (it has I

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

Le 12 janv. 2017 à 20:40, Mosè Giordano a écrit : > 2017-01-12 20:08 GMT+01:00 jfbu : >> I get the script raising to work fine, but under the condition >> of typing explicitely braces, i.e. >> >> \( x^{y^{z^a_b}} \) >> >> does the expected thing from the docs after

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

2017-01-12 20:08 GMT+01:00 jfbu : > I get the script raising to work fine, but under the condition > of typing explicitely braces, i.e. > > \( x^{y^{z^a_b}} \) > > does the expected thing from the docs after having set to > multi-level the ‘font-latex-fontify-script’, but the thing >

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

2017-01-12 20:01 GMT+01:00 jfbu : > Le 12/01/2017 à 19:57, Mosè Giordano a écrit : >> >> 2017-01-12 19:50 GMT+01:00 jfbu : >>> >>> Hi Mosè, >> >> >> What is "^" bound to? Issue >> >> C-h k ^ >> > > ^ runs the command TeX-insert-sub-or-superscript (found in

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

I get the script raising to work fine, but under the condition of typing explicitely braces, i.e. \( x^{y^{z^a_b}} \) does the expected thing from the docs after having set to multi-level the ‘font-latex-fontify-script’, but the thing about electric scripts does not seem to work \( x^y_z \)

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

Le 12/01/2017 à 19:57, Mosè Giordano a écrit : 2017-01-12 19:50 GMT+01:00 jfbu : Hi Mosè, What is "^" bound to? Issue C-h k ^ ^ runs the command TeX-insert-sub-or-superscript (found in LaTeX-mode-map), which is an interactive compiled Lisp function in ‘tex.el’. It is

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

Hi Mosè, thanks but regarding Le 12/01/2017 à 19:37, Mosè Giordano a écrit : In any case I strongly suggest you to set `TeX-electric-sub-and-superscript' to t, I always find it very useful also for single character script (in that case braces are redundant, of course, but they improve

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

Hi Jean-François, 2017-01-12 8:38 GMT+01:00 jfbu : > Hi All, > > in the attached screenshot with newly released 11.90, one sees > a feature which I find a bit disturbing: all the subscripts look > like they have a leading minus sign, where in fact it is the underscore > character. >

bug#25309: 11.89.8; multi-level script fontification stacks incorrectly

Le 12/01/2017 à 08:38, jfbu a écrit : The foo^{\psi_n} is ok but all foo_{bar} get the underscore aligned with exact middle of brace which creates (from a distance and with an ageing user) this impression about minus signs everywhere. 1. my screenshot is possibly dependent on the font, DejaVu

[AUCTeX-devel] Automatic adding of label to optional argument

Hi all, some packages like listings.sty have a label key since one cannot put \label in the body of the environment. I wrote a function which uses the standard interface of AUCTeX and/or RefTeX for inserting a \label and then moves the result into the optional argument. Please find attached a

Re: [AUCTeX] AUCTeX has a logo!

Mosè Giordano writes: > 2017-01-12 13:56 GMT+01:00 Arash Esbati : >> I have only one question reg. the placement of logo: Does it >> make sence to put the logo in the banner? Idea is attached. > > I already tried that last year, but didn't like it too much, because

Re: [AUCTeX] AUCTeX has a logo!

2017-01-12 13:56 GMT+01:00 Arash Esbati : > I have only one question reg. the placement of logo: Does it > make sence to put the logo in the banner? Idea is attached. I already tried that last year, but didn't like it too much, because I think it makes the header too high (or we

Re: [AUCTeX] AUCTeX has a logo!

Hi Mosè, Mosè Giordano writes: > yesterday a new version of AUCTeX was released and Tassilo promptly > updated the package on GNU ELPA and it is already live, so probably > many of you already got it. Let me thank all people who contributed > for this release come true. Again,