TeX, LaTeX and Friends - 2017-01-31

« first day (2284 days earlier) ← previous day next day → last day (2632 days later) »

6:19 AM

@PauloCereda egreg asked me to test this: http://tex.stackexchange.com/questions/351207/problem-with-arara-in-verbose-mode on Windows and I can confirm the error: whatever you write after `?` you don't see anything, but if you hit `enter` the letter appears.
I don't usually use verbose option, because I use `arara` within TeXstudio.
However, while I was testing I realized that if I chose `e` I got an error but now it works or, better, it starts Emacs (don't ask me why Emacs and not TeXworks, I don't know what I've done).

6:58 AM

@Jan Hallo! I remind you to introduce me to Don Carlos Tux. :):):)

1 hour later…

8:19 AM

@CarLaTeX Hello Carla, thank you. Lets see, what I can do. Don Carlos is at home, diving for fish, I guess.

8:38 AM

@Jan :):):)

@CarLaTeX You usually won't believe, what these guys do, if they think, the are not observed by you.

9:00 AM

@CarLaTeX hmmm I see. I have a Windows VM, I will take a look if I can reproduce.

@Johannes_B You will be so proud of me:

user image

@DavidCarlisle ooh

@DavidCarlisle: you could apply for the Doctor job.

@Jan they do unbelievable things!

@PauloCereda Thank you!

@DavidCarlisle Congratulations!

You fix bugs, people notice that the output has changed and report it: github.com/josephwright/beamer/issues/369 ;)

@PauloCereda I was the 15th doctor before I came back to sort out latex.

6

9:17 AM

@DavidCarlisle ooh the TeX doctor

9:37 AM

@DavidCarlisle i am proud of you :-)

@Johannes_B :-)

@Johannes_B ooh a penguin

There are probably children out there holding down spacebar to stay warm in the winter! YOUR UPDATE MURDERS CHILDREN.

@Silke Yes, I know

@Silke See github.com/josephwright/beamer/issues/352: Frank's right but I'm worried about what will happen when I fix it ...

@JosephWright freeze beamer for bug compatibility and write l3beamerxunitx using context?

9:49 AM

@DavidCarlisle :)

@DavidCarlisle If we can get the templates business sorted ...

@DavidCarlisle First l3sort though: need some decisions

@JosephWright apart from the last word, I was only half joking

@DavidCarlisle Yes, I realise that

@JosephWright see above, I have a badge

Christian Hupfer

@JosephWright: In your SVN L3 announcement from last Saturday you wrote that the 'deprecated' .value_required:n and .value_forbidden:n key property codes would be removed. I have updated this morning, the other additions are in there, but .value_***:n is still in there..., even in interface3 documentation

@DavidCarlisle Medium-term probably what I'd like to do

9:50 AM

@JosephWright I think you should fix it, but there are probably some people that will be unhappy about it. There are also people that are happy that bugs are fixed, but you won't hear those complain.

@ChristianHupfer Did I get it wrong: should say .value_required: and .value_forbidden: are removed

@Silke Yes, I know

Christian Hupfer

@JosephWright Oh my, yes that's a difference of course ... Thanks. This means I do not have to change code!. You really wrote .value_required:, not .value_required:n -- my fault

@Silke When Vedran and I took over, there were lots of complaints after we fixed the geometry bug saying 'the new people have broken beamer' even though we were doing it explicitly to fix the bug they had

@ChristianHupfer Phew

@Silke github.com/josephwright/beamer/issues/73 is a good example

@Silke Or more politely github.com/josephwright/beamer/issues/124

@Silke github.com/josephwright/beamer/issues/70 was also special: there was a bug in hyperref that was out of our control and 'live' for about 24 h :)

@DavidCarlisle Need to get some progress on some form of template structures: Chris will doubtless have some thoughts!

10:06 AM

@JosephWright: those issues are indeed 'special'. I guess the nicest way would be to try to group such bug fixes in certain releases, but you will still get the same kind of issues.

@Silke Yes, that's why I've currently got to branches: I did a bunch of fixes that went out as v3.37 and there have been some urgent follow-ups: at the same time I'm working on a new batch of fixes to go out some time in March

2 hours later…

12:29 PM

quack

1:23 PM

@PauloCereda boo

(and good coffee, by the way)

@yo' <3

(and loads of maths)

1:47 PM

@yo' ooh math and coffee

I heard mathematicians are machines that convert coffee into theorems. :)

@PauloCereda yeah, and skype soon, with my webcam aimed at my whiteboard :-)

@yo' ooh

@egreg I nearly gave you as an example in a comment just now:

As I say you could scale using the fontspec arguments, but personally I wouldn't do that. Lecturers can be wrong. Not everything they suggest is sensible. — David Carlisle 5 mins ago

@DavidCarlisle in a good way?

@DavidCarlisle In my course I say “10pt or 11pt is good, use 12pt or more only if you want to pad out”. In Italian we say “allungare il brodo”, that is, “adding water to the soup”.

2:01 PM

@PauloCereda s/good/accurate/

@egreg you don't need to translate for me!

@DavidCarlisle Do you say “lengthen the stock” in this sense?

@egreg No, not in English, but I am of course quite familiar with idiomatic Italian.

@DavidCarlisle :P

@egreg Quali sono i romani mai fatto per noi?

@DavidCarlisle Sorry, ungrammatical.

2:22 PM

@egreg "idiomatic"

2:50 PM

@DavidCarlisle LOL

2 hours later…

Christian Hupfer

5:10 PM

Is this the way the 'System' appreciates users trying to help?

user image

Thanks very much

@ChristianHupfer This was not an automated change

Christian Hupfer

@JosephWright Well, what else. I noted that somebody voted too much for my answers, of course, that's why I stated in my profile page to reduce this.

@ChristianHupfer (Not me but) There was active mod action taken to reverse a set of votes

@egreg -- sent you a piece of mail yesterday. seen it yet?

@barbarabeeton Not yet.

Christian Hupfer

5:15 PM

@JosephWright Well, most likely any vote by the same user has been invalidated then.

@ChristianHupfer That's likely, yes (I can't see voting specifics)

Christian Hupfer

@JosephWright: I hope the relevant mod enjoyed his action

@ChristianHupfer I can't comment on that beyond saying that moderators are expected to sometimes take actions that are not universally popular: rather the point of the role

5:33 PM

Quack!

6:27 PM

@ChristianHupfer See the positive: You can soon again celebrate 100.000. I bet none of the >-100.000-rep users had this chance!

@ChristianHupfer Wow! My record was –4630

@ChristianHupfer That algorithm is definitely stupid.

@egreg Not an automated task as already noted

@JosephWright It's more stupid, then.

7:18 PM

@ChristianHupfer I've just read your profile. Please once this issue being solved, notify us in here or in your profile so that we can upvote your answers. It is really hard and sad to not appreciate just beautiful answers, hopefully momentarily .

7:42 PM

@JosephWright Please, delete my account. Thank you very much!

7:54 PM

@Papiro If you insist

yes, please. thank you

@Papiro Actioned

8:32 PM

\foo[\relax x]{egreg is not alone} — David Carlisle 3 hours ago

8:49 PM

@egreg I see I attracted Bruno's attention

Christian Hupfer

@CroCo This issue has been done and every vote of the relevant user, even if it was only once a day (if at all) has been been removed. There's nothing to be solved left... Apparently it did not happen to me alone, of course.

9:07 PM

I'm hungry, I'll eat a foodnote! :) tex.stackexchange.com/questions/351442/…

9:22 PM

@JosephWright Maybe he has already solved the problem. ;-)

@egreg He did say he'd got an idea ages ago, and this is Bruno so ...

9:42 PM

@JosephWright Maybe this could be a different specifier, but also O{#2} is clear enough. As with the other features, it could be abused, but there's nothing one can do: duplicating an argument is useful as \section and the like commands show: saving an \IfNoValueTF test makes for less code duplication.

1 hour later…

10:51 PM

@egreg [0x00A1] = {0x0021, 0x0060}, -- exclamdown isn't that line the one that's Ok and [0x00A1] = {0x0021, 0x2018}, -- exclamdown the one that is wrong?

@DavidCarlisle Yes, I had made a previous test. I'll fix

@egreg thanks for tracking down where in luaotfload these things are set:-)

@DavidCarlisle I can't see why some of the ligatures are repeated.

@DavidCarlisle Also this is dubious

            [0x201C] = {0x2018, 0x2018},         -- quotedblleft
            [0x201D] = {0x2019, 0x2019},         -- quotedblright

@egreg agreed: it's pretty much nonsense to call any ligature for (input) characters above 127 "tex ligatures"

@DavidCarlisle Maybe XeTeX (tex-text, more precisely) does the same. Not sure.

11:02 PM

@egreg no luatex ligatures line 1 but not xetex

\documentclass{article}

\begin{document}

‘‘abc’’

‘\kern0pt‘abc’\kern0pt’


\end{document}

@egreg I could add that one to github issue or do you want to add a comment?

@DavidCarlisle Comment added

@egreg so I see, thanks

« first day (2284 days earlier) ← previous day next day → last day (2632 days later) »

Transcript for

Jan '1731

$TeX - LaTeX$ TeX, LaTeX and Friends

\begin{chat}

join this room
about this room

00:00

06:00

12:00

18:00

all times are UTC

$TeX - LaTeX$

site design / logo © 2024 Stack Exchange Inc; legal

mobile