« first day (3219 days earlier)      last day (1697 days later) » 

6:10 AM
Hi everyone.
1
Q: How do I include an animated preview of slides on stackexchange?

mimullerI found explanations of how to include still previews of compiled latex documents on stackexchange here, but my question is specifically for slides. Sometimes people include an animated preview of their slides, such as in the accepted answer here. What is the best way to achieve this?

I agree with Schrödinger's cat that this question has its place in the main site.
 
6:33 AM
@Schrödinger'scat I think as asked, it's right on meta "how do you post an animation", the non meta question that is linked is "hos do you make an animation" so an answer here would be "make an animated gif" and then link to the other answer for how to do that — David Carlisle 1 min ago
 
@DavidCarlisle Sounds good to me
 
@DavidCarlisle Wow, I agree with @DavidCarlisle! (We aren't talking about pizza, of course)
 
6:59 AM
@DavidCarlisle Indeed, the title of the question should have been changed.
 
 
3 hours later…
9:43 AM
@PhelypeOleinik Thanks. :)
 
9:56 AM
I seem to getting older rather fast ... ^^^
@DavidPurton I shouldn't have accepted your answer - it pushed me out of the palindrome circle which I had just reached through a downvote ;-(
 
@UlrikeFischer, well, I feel like any answer to a 200k rep user should get more than the default rep points. Maybe you could give me a large bounty (e.g., 500) and then work towards it again :)
 
@PhelypeOleinik: I just made a quick edit to your answer changing the syntax when conditionals are used with parametrized directives. Conditionals are always written in the end. :)
@PhelypeOleinik: by the way, perhaps it's worth mentioning short-circuiting when writing boolean expressions in conditionals. Depending on the evaluation, the order matters. E.g, b(x) || c(x), if b holds true, c(x) won't be evaluated. IIRC we need to disable short-circuiting in some cases, I think the syntax is b(x) | c(x)...
@PhelypeOleinik see here for a real case: github.com/cereda/arara/issues/121#issuecomment-488044374
It looks way better. Also note check = changed(entry) || check; as the term order matters! Due to the short circuit nature of ||, I forced changed(...) to be processed first, so we can ensure all file statuses are updated. It took me a couple of minutes to figure that out!
@PhelypeOleinik ^^ it indeed took me 10+ minutes to understand why my code was failing!
 
10:14 AM
@DavidPurton The problem is that with accepting I get 2 additional points, and so my rep ends with 4 instead of 2. No bounty can adjust that: You are not allowed to give away 48 points.
 
10:37 AM
@UlrikeFischer I'm sure you'll think of something ;)
 
10:52 AM
@PauloCereda Much appreciated :-)
@PauloCereda I was in doubt about that order, and arara didn't complain about the way I wrote it, so I assumed it was correct :-P
 
@PhelypeOleinik I believe it didn't complain because { ... } is an inline map, so it poorly evaluated it. :)
 
11:15 AM
@PauloCereda This user made the most complicated set of arara directives I've ever seen (ab)using this short-circuiting thing for changed(): tex.stackexchange.com/a/489687/134574 :-)
 
@JosephWright I triggered by accident a discussion about casefolding in bib entry keys: github.com/plk/biber/issues/278
 
11:26 AM
@PhelypeOleinik It's quite daunting!
@PhelypeOleinik it's challenging to come up with a set of conditionals like this because you need to know exactly what you are doing. Short-circuiting and term evaluation order might cause colateral damage!
 
 
1 hour later…
yo'
12:37 PM
@PauloCereda 15:00 Jekyll, 17:30 Hyde
3
 
1:25 PM
@yo' LOL
 
 
3 hours later…
3:56 PM
@yo' @PauloCereda I have a Russian friend who is a sound engineer. I have a Czech one too. A Czech one, too.
 
 
3 hours later…
7:04 PM
11
Q: Tex Quotes(UVa 272)

TwilightSparkleGiven a string, replace all left-double-quotes into two backticks and all right-double-quotes into two single-quotes. Left-quotes means the quotes that starts a quote. Right-quotes means the quotes that ends a quote. Quotes cannot be nested. You may assume that there are an even number of double...

Obvious answer is \catcode`\"=13\def"#1"{``#1''}, but that might well not count
 
@JosephWright Why not? :-)
 
@PhelypeOleinik I'm not sure how they might count 'input' and 'output': for example, my one line doesn't include the \bye we need
 
@JosephWright Usually they are flexible about the input/output, unless the question restricts it somehow. Some time ago I wrote an answer and people seemed to like it, even without the \bye :-)
 
7:23 PM
@JosephWright -- Wouldn't work if the left- and right-double-quotes use the Unicode codes.
 
@barbarabeeton Rules for the question say everything is matched, no nesting, also this is code golf so I doubt it has to be robust for arbitrary documents!
@barbarabeeton Question seems clear we are talking ASCII "
 
yo'
@JosephWright \let\par\bye might help :)
 
@yo' Adds bytes
 
yo'
Yeah I know
 
@JosephWright -- ASCII is implied, but I'd add that caveat to an answer.
 
7:28 PM
@barbarabeeton I think the 'local rules' are to ask in a comment before posting
 
7:41 PM
@JosephWright \catcode34=13 is shorter.
 
@UlrikeFischer True
 
@UlrikeFischer \catcode`"13 is shorter still
 
@DavidCarlisle i don't see a way to insert some \zz ;-)
we could build a format with \catcode=\z and \def=\zz ...
 
@UlrikeFischer That's probably one of the cheating things
@DavidCarlisle is the TeX golf expert: I'm waiting for his answer ;)
 
@JosephWright cheating is more fun ...
 
 
2 hours later…
10:16 PM
Speaking of cheating, tex.stackexchange.com/questions/505573/latex-typesetting is a question that plagiarizes from a paper about plagiarism detection, presumably in order to plagiarize better :-)
 
@ShreevatsaR Good spot!
 

« first day (3219 days earlier)      last day (1697 days later) »