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
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
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
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
>
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
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 \)
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
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
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.
>
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
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.
Have you discussed that in the thread already ?
(I read it back then but did
Tassilo Horn writes:
> Arash Esbati writes:
>
>> I think there is an issue with the code since I'm getting the
>> following in *Message* buffer:
>>
>> Error during redisplay: (jit-lock-function 1) signaled (void-function
>> copy-list)
>
> Ah,
Arash Esbati writes:
Hi Arash,
> thanks a ton for doing this.
You're welcome.
> I think there is an issue with the code since I'm getting the
> following in *Message* buffer:
>
> Error during redisplay: (jit-lock-function 1) signaled (void-function
> copy-list)
Tassilo Horn writes:
> I know what I did wrong. Will fix when I'm back home.
Hi Tassilo,
thanks a ton for doing this. I think there is an issue with the code
since I'm getting the following in *Message* buffer:
Error during redisplay: (jit-lock-function 1) signaled
>>> "Tassilo" == Tassilo Horn writes:
Hi Tassilo
> The problem was that the face/display specs for the script chars
> replaced the existing specs (math and sub/superscript), thus they were
> never shrunken. Now I prepend the spec which means that the shrinking
>
2017-01-05 14:01 GMT+01:00 Tassilo Horn :
> The problem was that the face/display specs for the script chars
> replaced the existing specs (math and sub/superscript), thus they were
> never shrunken. Now I prepend the spec which means that the shrinking
> happens also for ^_ which
I know what I did wrong. Will fix when I'm back home.
Bye,
Tassilo
Am 5. Januar 2017 13:23:00 schrieb Mosè Giordano :
2017-01-05 12:51 GMT+01:00 Mosè Giordano :
In my opinion, the top of the caret should line up
with the top of what it raises, see the "^{2}" in
Mosè Giordano writes:
> The bug, in my opinion, is that the "2" is slightly above of "^", and
> "3" is slightly below of "_". In particular the subscript is more
> problematic because it looks like it's written "-3" (ok, in my example
> there are braces, ideally remove them).
I
Mosè Giordano writes:
Hi Mosè,
> The bug, in my opinion, is that the "2" is slightly above of "^", and
> "3" is slightly below of "_". In particular the subscript is more
> problematic because it looks like it's written "-3" (ok, in my example
> there are braces, ideally remove
2017-01-04 18:43 GMT+01:00 Tassilo Horn :
> Anyway, my sense for aesthetics is very rudimentary so you have to
> explain to me where the bug is. What I did, however, is that I changed
> the default raise values from ±0.3 to ±0.5. So indeed the superscripts
> are a bit more raised
Hello everyone,
I can confirm that everything works. Thanks a lot!
Gennady
On 04/01/17 19:58, Tassilo Horn wrote:
> Mosè Giordano writes:
>
> Hi Mosè,
>
>> while trying to reproduce the problem reported by Gennady (I can
>> confirm it), I noticed another glitch. Now the
Mosè Giordano writes:
Hi Mosè,
>> while trying to reproduce the problem reported by Gennady (I can
>> confirm it), I noticed another glitch. Now the baseline of the
>> script is slightly above (below) of "^" ("_"), see the attached
>> screenshot (left: as it was before, right: as
Mosè Giordano writes:
Hi Mosè,
> while trying to reproduce the problem reported by Gennady (I can
> confirm it), I noticed another glitch. Now the baseline of the script
> is slightly above (below) of "^" ("_"), see the attached screenshot
> (left: as it was before, right: as it
2017-01-04 17:08 GMT+01:00 Mosè Giordano :
> Hi Tassilo,
>
> while trying to reproduce the problem reported by Gennady (I can
> confirm it), I noticed another glitch. Now the baseline of the script
> is slightly above (below) of "^" ("_"), see the attached screenshot
> (left: as it
Gennady Uraltsev writes:
Hi Gennady,
> Notice that $ is then "raised". Now erase the exponents by doing
> $1=x^2|$
> $1=x^|$
> $1=x^$
> The problem is that the closing $ is still raised.
I think I have fixed it. The unfontification code was only removing
display
Hi Tassilo,
while trying to reproduce the problem reported by Gennady (I can
confirm it), I noticed another glitch. Now the baseline of the script
is slightly above (below) of "^" ("_"), see the attached screenshot
(left: as it was before, right: as it is now).
Regarding the problem reported by
Hello Everyone,
I was testing out this new mode and there seems still to be some small
problem. The simplest case is as follows:
write the following
$1=x^2$
in the standard order and make sure that electric $ mode is off i.e. the
typing should look like this (with | being the cursor):
|
$|
2017-01-03 16:27 GMT+01:00 Tassilo Horn :
> Ok, there's a new variable `font-latex-fontify-script-max-level' which
> defines up to which scriptification level the script faces are applied
> again (thereby causing the decrease in font size).
>
>> In my pixelated example, position of
Mosè Giordano writes:
Hi Mosè,
>> Ok, great. Committed and pushed! I'm closing this bug then.
>
> Thank you, this is amazing!
>
> A couple of requests:
>
> 1) could you please mention this feature in doc/changes.texi?
Done!
> 2) is it possible to set a limit to scaling?
>
>
Gennady Uraltsev writes:
> Yep! Looks fantastic!
>>
>> Absolutely great. :-D
Ok, great. Committed and pushed! I'm closing this bug then.
Thanks,
Tassilo
signature.asc
Description: PGP signature
___
bug-auctex mailing
Yep! Looks fantastic!
On 03/01/17 12:17, Uwe Brauer wrote:
"Tassilo" == Tassilo Horn writes:
>
>> Tassilo Horn writes:
>
>>>> The only acceptable syntax is:
>>>>
>>>> $a_{b_c}$
>>>
>>> Ah, right. That makes things a bit easier.
>>> "Tassilo" == Tassilo Horn writes:
> Tassilo Horn writes:
>>> The only acceptable syntax is:
>>>
>>> $a_{b_c}$
>>
>> Ah, right. That makes things a bit easier. Basically, we can assume
>> that in $a^{b^c}$ the {b^c} part is already
Gennady Uraltsev writes:
> 2) LaTeX (or at least AMS) forbids expressions of the type $a_b_c$ and
> $a^b^c$.
>
>
> ERROR: Double subscript.
>
> --- TeX said ---
> l.106 $a_b_
>c$
> --- HELP ---
> There are two subscripts in a row in a mathematical
>
>>> "Gennady" == Gennady Uraltsev writes:
> Hello everyone,
> I am sorry for all the problems that have arisen. I wanted to contribute
> to the discussion somewhat.
This is for sure not your fault.
> 1) Personally I often have double subscripts i.e.
Hello everyone,
I am sorry for all the problems that have arisen. I wanted to contribute
to the discussion somewhat.
1) Personally I often have double subscripts i.e. expressions of the form
$
\int_{a_i}^{a_{i+1}}
$
(I am a PhD in math)
2) LaTeX (or at least AMS) forbids expressions of the
> Uwe Brauer writes:
> Hi Uwe,
> That might indicate that you are working in a field of math where there
> are few exponentiated expressions which are already exponentiated. But
> I don't think that exponents have grown out of vogue in general. ;-)
Well I
Uwe Brauer writes:
Hi Uwe,
> I have seen his shots, these are border line cases, which are used very
> little. Look I have written mathematics with latex over the last 25
> years and in countless occasions I have used ^or but never nested
> expressions and this is also true
> Uwe Brauer writes:
> Hi Uwe,
> Yes, exactly.
> Sorry, but I think there's no value in a feature which only works in the
> simplest cases and might be wrong otherwise. Have a look at Gennady's
> screenshots.
I have seen his shots, these are border line
Uwe Brauer writes:
Hi Uwe,
> > Given that it doesn't work and produces even wrong results, I removed
> > the complete feature, i.e., the values multi-level and invisible. I
> > don't see how it could be made working without parsing the actual math
> >
Uwe Brauer writes:
Hi Uwe and Gennady,
> Not really. I also don't really need that feature.
Given that it doesn't work and produces even wrong results, I removed
the complete feature, i.e., the values multi-level and invisible. I
don't see how it could be made working without
> Gennady Uraltsev writes:
> Hi Gennady,
> Right.
> Seems to be the case although only with scripts containing {...} with
> nested scripts.
> Yes, that seems to be the current behavior.
> I've also re-read the docs in the meantime
>>> "Gennady" == Gennady Uraltsev writes:
> Dear Tassilo,
> Actually no, the bug appears in all three versions: 24.3
I can confirm this. The bug appears in 24.3 and auctex from elpa.
Uwe
___
bug-auctex mailing
Gennady Uraltsev writes:
Hi Gennady,
> The relevant variables with apropriate values are:
>
> font-latex-fontify-script multi-level
> font-latex-scipt-display ((raise -0.3) raise 0.3)
>
> and the two faces
>
> Font Latex Superscript Face ((t
> (:height 0.8)))
>
>
Uwe Brauer writes:
Hi Uwe & Gennady,
sadly I'm unable to build emacs 24.3 or 24.4 from the sources and my
distro doesn't provide binary builds of any emacs version except for the
current one. :-(
>> Some care should be taken! After customizing the variable
>>
>>> "Gennady" == Gennady Uraltsev writes:
> Hello Everyone,
> I tried installing auctex thorough elpa in emacs 24.3.1 . It was
> difficult as it gave errors quite often, however after trying again
> several times I managed to do it.
I did this also,
Sorry,
it was version 24.5
Gennady
On 01/01/17 15:10, Gennady Uraltsev wrote:
> Hello,
>
> Sorry for the delay in responding. I powered up an Ubuntu 16.10 virtual
> machine and installed emacs available there (24.4) the same problem is
> there. Attaching screenshot.
>
> Gennady
>
> On
Hello,
Sorry for the delay in responding. I powered up an Ubuntu 16.10 virtual
machine and installed emacs available there (24.4) the same problem is
there. Attaching screenshot.
Gennady
On 01/01/17 12:51, Uwe Brauer wrote:
>
>> Mosè Giordano writes:
>> Hi Gennady, Uwe &
>>> "Tassilo" == Tassilo Horn writes:
> Uwe Brauer writes:
>> I have 24.x,[1] but I have to change my init file because right now I
>> obtain on start the following error:
>> Warning (emacs): Unable to activate package `with-editor'.
>
Uwe Brauer writes:
> I have 24.x,[1] but I have to change my init file because right now I
> obtain on start the following error:
> Warning (emacs): Unable to activate package `with-editor'.
with-editor is used by magit, as far as I know.
> Required package `emacs-24.4' is
> Mosè Giordano writes:
> Hi Gennady, Uwe & Mosè,
> [CC'ing Uwe because I know he uses this feature.]
> Does anyone of you have an older Emacs copy (22.x, 23.x, 24.x)
> installed and can check what the results are with that?
Hm I run emacs -Q load a simple
> Mosè Giordano writes:
> Hi Gennady, Uwe & Mosè,
> [CC'ing Uwe because I know he uses this feature.]
> I just had a look and Gennady is correct in that there is an issue here
> although what I get is a bit different from his observations.
> With
Mosè Giordano writes:
Hi Gennady, Uwe & Mosè,
[CC'ing Uwe because I know he uses this feature.]
>> The multi-level fontification was introduced by
>> Tassilo Horn with commit 513490f on 2015-09-03.
>
> Wow, I didn't even remember such change! My memory is failing :-(
>
>
Mosè Giordano writes:
Hi Gennady, Uwe & Mosè,
[CC'ing Uwe because I know he uses this feature.]
>> The multi-level fontification was introduced by
>> Tassilo Horn with commit 513490f on 2015-09-03.
>
> Wow, I didn't even remember such change! My memory is failing :-(
>
>
2016-12-31 15:57 GMT+01:00 Gennady Uraltsev :
> Hello,
>
> I use Emacs a lot but I am not very familiar with coding. During this
> winter break I tried to look through the code base a bit to learn.
>
> The multi-level fontification was introduced by
> Tassilo Horn with
Hello,
I use Emacs a lot but I am not very familiar with coding. During this
winter break I tried to look through the code base a bit to learn.
The multi-level fontification was introduced by
Tassilo Horn with commit 513490f on 2015-09-03.
I'll see if I manage to write a patch. The most
Hi Gennady,
2016-12-31 15:12 GMT+01:00 Gennady Uraltsev :
> Hello,
>
> I have discovered multi-level fontification of sub and superscripts.
Honestly, I didn't even know this feature!
> However it seems slightly broken. While the scaling of the text defined
> in the
56 matches
Mail list logo