I have no idea how to suggest migration, nowadays. I suggest migration of tex.stackexchange.com/questions/360132 (see comments) to the emacs stackexchange.

@BrunoLeFloch Flag

@BrunoLeFloch I've sent it across

@UlrikeFischer Live updates?

@JosephWright ? Sorry what do you mean? (My talk wasn't yet, until now we had two interesting talks about latex in humanities (crititical editions))

ooh

A question about the site: If I commented on a question that has now been deleted. Can I somehow find back to that deleted question? or does that need a certain level?

@daleif You should be able to see deleted questions

@JosephWright but where? I was looking in my activities, and could not find my comments from this morning

@JosephWright but apriori only if you have the link

@daleif try finding it in tex.stackexchange.com/tools if it's recent

Mae fy hofrenfad yn llawn llyswennod

There's a cat somewhere.

And a cow that seems to use L'Oréal products.

@PauloCereda There are few moments when I am not proud to be a German. You found one.

@MarcoDaniel boo <3 This is great!

My other favourite video:

I want this hat so much! :)

@Johannes_B, @ChristianHupfer ^^ :)

I have a thesis to write and here I am listening to a yodelling bloke wearing a weird hat. :)

@DavidCarlisle, @JosephWright -- i could probably make a real question out of this, but it's very specialized. i'm writing a tome on indexing, and need to recommend protecting macros (like \textit) from expanding when the \index entry is in a moving or restricted environment (e.g. caption or footnote). is it better to use \protect or \string?

@yo' thanks, did not know that page

@PauloCereda I warned you!!!!!

@ChristianHupfer <3

@barbarabeeton \textit and friends are robust anyway so \protect won't help, the issue is usualy how best to stop \index attempt at verbatim

@PauloCereda That's the 5th weapon of Spanish Inquisition: Yodelling... another form of torture ...

@PauloCereda Ok Germans are drinking beer and wearing leather trousers

@ChristianHupfer LOL

@ChristianHupfer Not as efficient as the comfy chair. :)

@MarcoDaniel oh no

@PauloCereda Yes, nothing beats the comfy chair... or poking with cushions...

@ChristianHupfer we could bring Schnappi. :)

@PauloCereda Hm, this is not argument clinic but you're looking for an argument, actually?

@ChristianHupfer I wish to register a complain, actually. :)

@MarcoDaniel You forgot the Schweinshaxe and Sauerkraut ;-)

@daleif works only for recent deletions though :-(

@DavidCarlisle -- well, okay. (when i first started writing, tex live 2012 didn't have robust \textit. but the requirement still holds for uncontrollable user-defined macros.) how do you suggest changing \index so that it doesn't take arguments verbatim?

@PauloCereda Desk of complaints has closed ... come back in 2047 please ;-)

@ChristianHupfer NOTLOB

@PauloCereda Ipswhich

@ChristianHupfer for a minute, I read kpsewhich :)

@PauloCereda Don't be silly -- nobody lives in kpsewhich :D

@ChristianHupfer LOL

@PauloCereda: What about the Icelandic Saga?

             HELP THE EXCITING ICELANDIC SAGA
             C/O MATCH OF THE DAY
             BBC TIt
             THE LARCHES
             26 WESTBROOK AVENUE
             FAVERSHAM
             KENT

@ChristianHupfer ^^^ :)

@barbarabeeton textit has always been robust I think but the verbatim business is a pain (usually shows up as entries differing by a space, so being duplicated) you can do tex.stackexchange.com/questions/176439/… but you can't do it as a global change as you'd break any uses that really needed to be verbatim (eg indexing a fragile command)

@PauloCereda Ah, with naughty words .... KENT ;-)

@ChristianHupfer :D

It's being a while since our last cricket news...

Or fencing.

@PauloCereda Don't open Pandora's Box .... please

github.com/dante-ev/dtk-bibliography

@DavidCarlisle -- now that i reread what i've actually written, the space is the reason given for the need for protection. the \mbox suggestion you've given in the cited answer isn't acceptable because of the hyphenation and line-breaking considerations mentioned in a comment. either \protect or \string works very well, and with limited side effects. so, which is better?

@PauloCereda For you ;-)

@ChristianHupfer ooh :)

@ChristianHupfer I never watched it. Harry Potter too.

@PauloCereda Doubled boo!!!!!!

@ChristianHupfer :)

@barbarabeeton oh it doesn't have to be mbox, \newcommand\foo[1]{#1} would be enough and wouldn't stop breaking

@ChristianHupfer What's LoTR?

@barbarabeeton no \protect in general won't work and \string only works if you have disabled the verbatim, otherwise you will get verbatim \string I think best way (which I suspect is also on an answer here somewhere) is to open up the internals and replace teh verbatim handling by e-tex \detokenize so you get a form of verbatim that works teh same way in macro arguments as not

@DavidCarlisle -- well, i don't want to advise to define something new, and i can't think of a suitable existing alternative. what's wrong with \string (other than it's a primitive, and thus not "latex") or \protect?

@MarcoDaniel Lord of The Rings...

@barbarabeeton they don't work

@DavidCarlisle -- you answered while i was typing. i'll have to look back at my tests. i'm pretty sure i have one that demonstrated that \string worked. i'll take a look at your other answer and do some more testing. thanks. this may be insoluble for the present purpose.

@ChristianHupfer Something I've never seen and I have and will never regret it. ;-) -- My wife loves the movies. In such situations I am happy having an office ;-)

@MarcoDaniel :)

@barbarabeeton \string will work in cases that the index is in a macro argument (making up for the failure of verbatim there) but if you use \string in a context where the verbatim works then you get verbatim \string in the index. so it can't be used as a general index markup.

@MarcoDaniel A great Boo to you too ;-) ....

@DavidCarlisle -- i don't expect the audience this is directed at would be likely to use \index in a verbatim environment, but that's something that can be warned against. the intended audience is primarily ams authors, but i was considering also posting the document to the (now defunct?) latex.sx blog.

What type of personality do you have to have to begin a SE answer with "I can't say for sure but ... "? #EL&U

@AlanMunn -- that's remarkably inconsistent ... it might happen here on tex.sx (though not expected), but on el&u? (read interrobang here.))

@barbarabeeton Sadly it's remarkably consistent on that site. People seem very happy just to say things freely admitting in the answer they don't know what they're talking about.

@AlanMunn -- somehow, i thought that's what comments are for. maybe that's why i gave up following el&u and went off to ell instead.

@barbarabeeton I don't spend much time on either. I have occasionally posted to EL&U but quickly get tired of it.

@yo' Strange, I was looking for the posting about a missing datetime2 in TL16, but it has disappeared.

@AlanMunn I found a very nice answer that starts by saying that yes, haphazard is a unique word which has ‘ph’ and is not pronounced as ‘f’. Then it goes on by showing six other examples. Probably the meaning of unique is not so clear.

@egreg Well given that the locution very unique is widespread, unique is now a gradable adjective.

@AlanMunn Like equal? ;-)

@egreg equal has always been gradable. :)

@AlanMunn The problem is you borrowed from Latin without knowing it. ;-)

@barbarabeeton no that's not the point it is using `\index in (say) footnote and not in footnote.

@egreg I blame the French.

@AlanMunn coin coin

@egreg What have the Romans ever done for us?

@DavidCarlisle -- but i've already said that every instance inputting a particular index entry must be identical, so that's covered. (though a reminder might be in order in the appropriate context.)

@egreg I don't know if I've posted this before, but the following is a table showing people's judgements on "how good an exemplar of the category even/odd number" is on a scale of 1-7 with 1 being the best. (Number judged is on the left column, mean score on the right.)

@AlanMunn Funny!

Source: Sharon Lee Armstrong, Lila R. Gleitman, Henry Gleitman. 1983. What some concepts might not be, Cognition, 13-3, 263-308, dx.doi.org/10.1016/0010-0277(83)90012-4.

@AlanMunn -- that's a rather semantically loaded way of expressing the question. i could interpret it as meaning "if you had to specify a (random) even (or odd) number, would you likely specify this one?" that's quite different from "is this number even or odd?" (wonder what the answers would be to that, if given the options "even", "odd" or "not sure".)

@barbarabeeton I think we are talking cross purposes:-) but if you mean people should go \index{\string\fragilecommand} then that will work inside footnote to index \fragilecommand but will not work at the top level as it will be read verbatim and index \string\fragilecommand

@barbarabeeton Yes, that's exactly the point. But people have made claims that such behaviour in other categories is evidence of some sort of prototype theory of meaning.

@barbarabeeton If you ask the following question: "Does it make sense to rate the items in this category for degree of membership in the category?", people will say No 100% to "odd" and "even" (although only 83% to "female"). But even after declaring that it makes no sense to grade the category, they will still grade it when asked.

@DavidCarlisle -- okay. something to test. what i need to describe is something that will work in all likely contexts in books (to be) published by ams. (but as i said, i'm trying to write it with the intention that it will be usable by a general audience, not necessarily for someone who's indexing the companion or a .dtx file.) would you be willing to read it when i've completed my next revision?

@AlanMunn -- yikes! does the article you cited as the source of the table go into such concepts? i.e., might i comprehend this better if i read it (or attempt to)? (i'm neither a philosopher nor a statistician, so i suspect some arguments are going to go right over my head.)

@barbarabeeton Yes, it's a pretty readable article. I can send you a copy if you like.

@AlanMunn -- your link works for me, so no need, but thanks. (i'll see what i can make of it.)

Is there a ranking of the valuable flair of all combined Stack Exchange profiles?

@egreg: You still have a ways to go... ;) ^^^^

@Werner ooh David is on the list

@Werner Well, not bad at all!

Yup, network-wide ranking.

@PauloCereda Way behind. ;-)

@egreg ooh :)

@egreg Ha ha!

@PauloCereda second box seems pretty accurate

@DavidCarlisle From my desk... :)

Microsoft describes Visual Studio Code as a source code editor that's "optimized for building and debugging modern web and cloud applications." In fact, VSC turns out to be rather inefficient when it comes to CPU resources. Developer Jo Liss has found that the software, when in focus and idle, uses 13 percent of CPU capacity just to render its blinking cursor. Liss explains that the issue can be reproduced by closing all VSC windows, opening a new window, opening a new tab with an empty untitled file, then checking CPU activity. For other macOS applications that present a blinking cursor, l…

LOL

@PauloCereda EMACS stands for Electric Machine Access Gear Support in that sign.... not for the one and only EMACS ;-) You've misunderstood the message...

@ChristianHupfer boo :)

@PauloCereda It's a typo anyway: EMAGS ... ;-)

@PauloCereda I am surprised that it is only \SI{13}{\percent} ;-)

@ChristianHupfer :)

@ChristianHupfer :D

@PauloCereda Since the human eye has a time resolution of about 1/20 second at most (i.e. 50ms) it is very funny to have a blinking cursor at 16 ms ... this should not be recognized as blinking at all ... this is well - invested CPU resource ;-)

@ChristianHupfer Do ducks blink?

Oh. My.

@PauloCereda Let's connect them to a AC source and see whether they blink ;-)

@ChristianHupfer Go away, you are mean. :)

@PauloCereda Alternate facts? ;-)