« first day (585 days earlier)      last day (4007 days later) » 

12:13 AM
Just stole it from John Baez' blog...
@percusse Wow!!
@percusse: could I ask a very, very newbie TikZ question? /blushes
@PauloCereda No you will be super good in two days. And I won't get any reps anymore :P
fire at will please
@percusse <3
    \node[draw,inner sep=5pt, minimum height=1.0cm, minimum width=1.0cm,thick,rounded corners=8pt,font=\large\bfseries] {#1};%
I'd like to make the rectangle width to be the full text width.
But I had no idea how. :(
I'm sure I'm missing something obvious. :(
12:25 AM
ah just to confirm you mean to have the length of \textwidth
Can I use it there? :)
let me test before i reveal my stupidity :)
I thought this wouldn't be too TikZy. :)
    \node[draw,inner sep=5pt, minimum height=1.0cm, minimum width=\textwidth,thick,rounded corners=8pt,font=\large\bfseries] {#1};%
And now we go for the next section of

\drawtheme{Theme Hospital}
This seems working :)
Thank you thank you thank you thank you thank you very much! <3
Love the MWE. :P
12:29 AM
@PauloCereda I wish I could say that I did something :) You had the solution anyway.
Instead solve this illusion : youtube.com/watch?v=PpM8bl64wDk
@percusse Of course you did! :) You led me to the right way.
@PauloCereda I just reinstalled Reason 5 for more procrastination.
@percusse :)
My procrastination doesn't grow on an AP, but on a GP. :P
Wow, geometric progression.
@PauloCereda Like the Shepard Tone?
@percusse Wow. I guess so. :) (Wikipedia tried to help me but it was in vain) :P
The sample sound it has sounds like a horror movie. :)
12:37 AM
@PauloCereda Oh sorry, you missed the linked that I've sent just above i guess
@percusse Oops sorry, I'll check it. :)
@percusse: I'm waiting for an explosion! It's very cool! :D
@PauloCereda That's the illusion (just like the PhD). You feel some elevation but in fact it just repeats itself identically :)
@percusse Fantastic! :)
@PauloCereda If you have your headphones near you try the virtual barbershop. We used to have fun with async stereo in undergrad.
@percusse LOL Luigi! :P
12:44 AM
@PauloCereda :-)
Very very cool. :)
That razor makes me very uncomfy
@percusse Me too. :) It looks like it's gonna cut our ears. :)
1:03 AM
Bed time! Good night, friends! :)
@PauloCereda Good night!
6 hours later…
7:28 AM
user image
Last night's quiz.
3 hours later…
10:00 AM
Why is \[...\] preferred over $$...$$ for display math?
Probably a question asked 1000 times on this site, but hard to search for [` and $$`
10:11 AM
OK, I've found it:
Q: Display math deadly sin in l2tabu

Jasper LoyAs a follow-up to Why is \[ ... \] preferable to $$?, what really is wrong with the vertical spacing as stated in l2tabu introduced by using $$...$$ instead of \[...\]? As there does not seem to be an elaboration of this in l2tabu except for the remark that vertical spacing is modified and rende...

@AndrewStacey Very nice, Andrew! :)
10:35 AM
One more vote needed:
Q: How do I include a \section*{} in a \tableofcontents?

notfedI've got something like \documentclass{article} \begin{document} \tableofcontents \section*{About this Article} \section*{About this Author} \section{First Step} \section{Second Step} \end{document} My table of contents won't show the "About this Article" and "About this Author" sections. ...

11:26 AM
A: Is there a standard package to create a table like this?

Brent.LongboroughNote: something appears to be wrong with the formatting engine. Please bear with me until I get it sorted on meta. Here's an outline answer using tabularx and tikz. I apologise for (a) Not filling in all the text and (b) not tuning the horizontal fit and spacing. \documentclass[10pt]{article...

Is there something wrong with the SX engines?
@BrentLongborough It's quite tricky to insert code inside a list. :)
I think it's 4 spaces + 1 from the item.
@PauloCereda There is no list.
@MartinScharrer The first revision from Brent has a list, I'm assuming from there. :)
A harmless 1.<space> is enough for Markdown treat it as a list. :)
11:48 AM
@PauloCereda I took the list out, and it was still bad, but after Martin's edit it's OK (Thanks, Martin). I wonder if it was my leading tabs that did it (ie some lines started with space space space space tab)
@BrentLongborough Don't worry, your input was actually right. :) The secret was to add 8 (eight!) spaces instead of 4 for making the code part of the list, or inserting an invisible HTML comment <!-- hello! --> before your code, in order to "cancel" the list scope. :)
@Brent: I added an answer to your meta question. :)
Oops, @MartinScharrer updated his answer. :) I'll probably delete my answer. :)
Ooh I can define styles with TikZ and use them later!
12:20 PM
@PauloCereda I didn't see you answer when I was updating mine.
But I think the list/code issue is anyway mentioned already in another Q
12:37 PM
@MartinScharrer Indeed. I couldn't find it too. :(
12:53 PM
Newbie question!
I'm following Joseph's great answer here:
Q: LaTeX3: how to access package options

AlexGIn my package I intend to write in expl3 syntax, how can I get access to the list of options passed to it on the document level via \usepackage[<option list>]{my-l3-pkg}? I know more or less how to define and set keys using the functions provided by the l3keys package. I don't know yet, wh...

And came up with this silly example:
\ProvidesExplPackage{mypkg}{2012/06/07}{1}{A demo}
\keys_define:nn {mypkg}
    night .code:n = \def\myvalue{night},
    day .code:n = \def\myvalue{day}
\ProcessKeysOptions {mypkg}

\newcommand{\greetings}{Good \myvalue!}
It works like a charm, except "Good day!" is shown as "Goodday!". Is this because LaTeX3 ignores spaces?
@PauloCereda Yes. Use \space or ~ to get a literal space.
(If~ you~ look~ at~ the~ source~ of~ a~ LaTeX3~ file~ you'll~ see~ lots~ of~ things~ like~ this)
@AndrewStacey Ah great! Thanks Andrew! :)
@PauloCereda And never put ~ at the start of a line (TeX by rule ignores spaces there): if you need to break a line of supplied text, break it after ~
@AndrewStacey Since the tilde is a diacritical mark in Portuguese, I need to type ~ + [space] in order to get a proper ~. :P
@PauloCereda NO!
1:03 PM
@egreg Uh-oh!
Just what Marcel Marceau answered to Mel Brooks in "Silent Movie". :)
@egreg :)
The tilde key is set as a "dead key" for Portuguese, so I can easily write words like "cão". :)
Precisely, he said "NON", being French. :)
@PauloCereda Think of a space-with-a-tilde as a LaTeX3-space and then you'll type ~[space] every time.
@AndrewStacey Good idea. :)
@egreg Out of curiosity, if I use Good~ \myvalue, is still possible to have a line break?
1:07 PM
@AndrewStacey true although ideally you wouldn't see too many of those as the coding file with the l3 syntax shouldn't have too many natural language strings, which would normally be accessed via a command defined elsewhere (to allow localisation apart from anything else) like \figurename in 2e/babel
@PauloCereda It doesn't matter how you input ã: in the TeX input ~a will never produce ã; but if you put ã in the .sty file it will be interpreted as usual. However, it's best not to rely on UTF-8 characters; better write \~a in a .sty file, unless it's specific for XeTeX or LuaTeX
@egreg Got it. :)
@DavidCarlisle Been spending too much time looking at how the messages are displayed for things like \prop_show:N \my_amazing_prop.
@AndrewStacey yes well that's more low level tracing than user level messages I would guess(not having looked for 10 years:-)
@PauloCereda Well, ~a may produce ã in a LaTeX document, if ~ is used as a shorthand (it used to be in Spanish, but now it's deprecated). But this would hold only after \begin{document} anyway. So what's read before doesn't obey the shorthand, generally.
1:10 PM
@egreg I see. :) Good to know. :)
@PauloCereda note the ~ is not the normal plain tex latex2e active ~ for a non breaking space it s a real (catcode 10) space character, so for example it is discarded if used after a command name. Any definition of active character ~ for use in the main document is not looked at at all in this context.
at least I think it is...
@DavidCarlisle Ah! I was wondering if it was a "real" space. :)
@DavidCarlisle As you said. Hey! You're still at 90, today. It's time to work!
@egreg time to work, true but not on TeX:-)
@egreg Gosh! I'm temporarily ahead of David! Mind you, today's reputation is currently 2/3 for a recycled hash and 1/3 for something that actually took some work (including loading the trace package).
1:16 PM
@egreg There are some juicy TikZ questions for @David. :)
@PauloCereda Yes, I'm very surprised he tackled none of them.
@egreg :)
1:51 PM
After I used the L3 sorcery, I used \ExplSyntaxOff to come back to my other definitions. Is this the right way? Since I have some TikZ stuff going on, it was easier for me to disable the L3 syntax, so my spaces would be preserved (otherwise I had to go with colorbox/.style={draw=black!30,top~ color=white...)
@PauloCereda That's the way to go with TikZ. Also the colon has a special meaning in TikZ. This makes it quite difficult to make it cooperate with expl3: you can't use the "programmer syntax" when working with TikZ/PGF.
@egreg Thanks! I'm really happy with this new experience. :) I'm falling in love with this L3 stuff. :) Out of curiosity, can I go with \ExplSyntaxOff when dealing with Tikz and use \ExplSyntaxOn right after for more L3 goodies? :)
@PauloCereda As many times as you want.
@egreg Sweet! :)
2:26 PM
@PauloCereda yes it's just like \makeatletter/makeatother and similarly should not be needed explicitly once all code is in its proper file types. (So it's needed quite often when mixing 2e and l3:-)
@DavidCarlisle This whol L3 experience is being very nice! :D
@PauloCereda but try to avoid mixing the stuff inside a block too much (best not at all). I know it is tempting to go \expandafter or \def or \let (and I have been guilty about that for a long time initially) but it really helps if you force yourself to use \cs_set_eq:NN etc thoughout. It is a bit more work initially but once you get used to it it helps you to better think in the expl3 methology
@PauloCereda What did you do?
@FrankMittelbach I'm trying to stick only with the new approaches (xparse is fantastic). :) So far, it's been a really nice experience. :) I put all the TikZ part together, like sit in the corner. :)
@MarcoDaniel I'm rewriting/porting my songbook to a clearer code. :)
2:42 PM
@PauloCereda Great
@PauloCereda you are lying :-) ... just look at the piece of code you posted earlier in chat
@PauloCereda this one
@FrankMittelbach That was the previous one, don't accuse me! :P
@FrankMittelbach I'm ashamed of that code. :P
3:00 PM
@PauloCereda This isn't enough ;-)
@MarcoDaniel OK, here it is! :)

\ProvidesExplPackage{vozes}{2012/06/07}{1}{Vozes configuration}

\keys_define:nn {vozes}
    color .code:n = \toggletrue{usecolors}


\iftoggle{usecolors}{\tikzset{colorbox/.style={draw=black!30,top color=white,bottom color=black!20}}}{\tikzset{colorbox/.style={}}}
This is what I've done so far. :)
But there's much more to come.
@PauloCereda Some improvements
@MarcoDaniel <3
@PauloCereda l3keys define a key bool:N which should be used
@MarcoDaniel Oh!
3:02 PM
\keys_define:nn {vozes}
    color .bool:N = \l_vozed_color_bool
Told you my conversion was recent. :)
And now you can use
\bool_if:NTF \l_vozed_color_bool { True } { False }
Oh my! I'm gonna test it right now! :D
@PauloCereda It the correct syntax and the meaning of the variable was explained yesterday ;-)
@MarcoDaniel However, there's the problem of using TikZ code in expl3 mode.
3:06 PM
@egreg Only if you use : ;-)
@MarcoDaniel Uh-oh: The key property '.bool:N' is unknown. :)
@egreg The declaration must be done after \ExplSyntaxOff
@PauloCereda .bool_set:N or, better for a global option, .bool_gset:N
Sorry it is .bool_set:N
@egreg gset will only work for the svn version (I believe)
@egreg @MarcoDaniel Thanks it works! :)
3:09 PM
@MarcoDaniel I have it in my interface3 manual.
@egreg Ah ok -- Please see: github.com/latex3/svn-mirror/commit/…
I was wrong
I want a LaTeX3 T-shirt!
@egreg: I want to write a small xindy style to use LaTeX commands for formatting. However can you help me to collect all possible input methods of \index? I will describe it. If you write \index{foo} the following think will happen:
\prop_put:cnn { \l_indexentry_foo_prop} {entry} { foo }
\prop_put:cnn { \l_indexentry_foo_prop} {format} { }
Now the question: which properties do I have to set?
@MarcoDaniel It's difficult to say: the page format declaration is specified like in \index{foo|textbf}.
Or there is \index{foo|see{bar}}
@egreg Of course I have to redefine the command \@wrindex
3:25 PM
@MarcoDaniel Of course. I wouldn't. :)
I don't think that allocating a property list for each index entry is the way to go.
@egreg This is the only way to hack xindy. here a simple example ( I know it isn't useful but it demonstrate my suggestion)

\makeindex[program=texindy,options={-M mystyle.xdy -t \jobname.ilg}]
;;; xindy style file
(markup-locclass-list :open "\dotfill" :sep "")

(define-attributes (( "textbf" "default" "*")) )
@egreg To you have another idea?
Have a look at the generated ind file
The aim must be to remove the attribute declaration of \index{foobar|textbf}. This is the only way to allow LaTeX commands.
3:42 PM
@MarcoDaniel There's a different problem, however: if you want to use UTF-8 characters, then \protected@write is not the way to go. You get \IeC{\"a} for ä. Probably switching to \unexpanded will be necessary.
With other problems, of course. :(
@MarcoDaniel would you please remove all the center? They only add confusion.
@PauloCereda now that's an idea ... as in 20 years late but still coming ...
@egreg Yes I will. Time for dinner
@FrankMittelbach Did you see my logo attempt? :)
@PauloCereda sorry no ... point me to it please; that is faster than me searching for it
@FrankMittelbach Sure! :) It took me a while to find it too: i.stack.imgur.com/xRbnX.png :)
4:03 PM
@egreg I believe that's a really bad design flaw of inputenc. xmltex for instance (yay @DavidCarlisle !) just transforms utf8 characters into a control sequence, keeping the code, which can then be redefined in different contexts to do different things (for instance, yield the utf8 code back). What happens if you use utf8 characters in a \label.
I'll submit my first python script to the author of this presentation, which prints entry level != idiot and a 2500€ worth of font files attached.
I understand that's a historical legacy from pre-unicode times, to allow switching input encoding, for instance to load files with different encodings without having a common global coding system to map everything to. Still, it has severe disadvantages nowadays.
@StephanLehmke Agree entirely: I'm very much of the 'LaTeX3 should strongly push UTF-8 input' school of thought
@PauloCereda nice. do you have other proposals? I have to give a talk or two in July
@JosephWright It's not even neccesary to push UTF8 input. It would be sufficient if inputenc just transformed any encoding into UTF8 (assuming all characters can be mapped ;-) .
4:07 PM
@FrankMittelbach I can make other suggestions, if you want. :)
@PauloCereda Just out of curiosity: Is that a real "e" in the middle? It looks like my children learn to write a lower case "z" in handwriting.
@StephanLehmke It's a fancy 3. :)
@PauloCereda Oooh blushes
@StephanLehmke Subtle catch for LaTeX3 advertisement. :P
@PauloCereda why not? as due to all the good guys like @Joseph, @Will, @Bruno, to name a few it is gathering momentum again so a logo at some point would be nice
4:12 PM
@FrankMittelbach I'd be honoured to draw some sketches. :) I'll send you some attempts. :)
@StephanLehmke High bit UTF-8 characters should expand to themselves when in a \protected@write. Probably defining them with \protected would be better, but it's e-TeX, you know. And there's a strict policy on this, I believe.
@egreg But as you said, they aren't recognizable as UTF8 any more when they have been read by inputenc.
@StephanLehmke Each of the bytes is active and has a definition. If this were given as \protected\def they would be written literally. And then the input would recognize them again.
@StephanLehmke the idea of inputenc and xmltex is really the same there though that any iinput is normalised to an internal form. inputenc uses (7bit ascii safe) command sequence xmltex uses (essentially) utf8. At the time that inputenc was written unicode didn't have enough math characters defined to support even a basic set of tex math commands, so normalising to utf8 wasn't really an option 9and it's not particularly convenient normal form for classic tex anyway)
@DavidCarlisle In that case it should be possible to add something to \protected@... so that UTF8 characters transform back to UTF8, as it works with xmltex.
4:20 PM
@StephanLehmke yes but no. inputenc design is that you can have a chapter written in utf8 that writes a toc entry that gets read back in the frontmatter where the current encoding is latin-2 or something. So writing the characters as utf8 would be wrong, which is why it goes to some lengths not to do it:-)
@DavidCarlisle One might have a "strictutf8" option, where changing of input encoding is forbidden.
An alternative design would be to read all auxiliary files back as utf8 whatever the document encoding, but any such design change would have to be for a future version of latex...
@PauloCereda yes please
@egreg we could have a strict version where only 7bit ascii were allowed and you had to write in English. That way 90% of the complication would go... We could call it TeX2
@DavidCarlisle Well what about some Unicode based command syntax which always denotes a unicode character no matter what the current input encoding is. For instance, in XML &#xyz; notation always encodes unicode points no matter what the declared encoding of the XML file is.
4:23 PM
@DavidCarlisle You'd have to define a map "encoding" to UTF-8 for each of the (many) 8 bit code pages.
@FrankMittelbach Sure! I'll send them by the middle of next week. :)
@egreg that's what xmltex does (well it does a few and let's users produce others if they need them)
@DavidCarlisle XML <3
@StephanLehmke can't you go ^^abcd in xetex (showing my ignorance here:-)
@DavidCarlisle And it really doesn't matter whether the operating system understands UTF-8, as TeX works strictly on 8 bit input and output. But there's the ^^ convention, you see. :(
4:26 PM
@DavidCarlisle I think input encodings are irrelevant to 16+bit engines anyway ;-)
@StephanLehmke When LaTeX will require a Unicode engine. ;-)
@DavidCarlisle You can use ^^^^abcd with both XeTeX and LuaTeX.
@egreg Probably never. Hence it's not much use to speculate about notations which are only possible on such systems.
@StephanLehmke Browsers are 16bit engines and last time I checked utf8 was still only just creeping towards being the most common encoding. The thing is end users produce what they produce and typically it's quite hard to see what encoding a file is in if the software being used detects the encoding and does the right thing regardless.
@DavidCarlisle I used this for recognizing if the engine is Unicode or not: define something to expand to ^^^^0000, which is ignored in Unicode engines, and compare it to \empty. Then I discovered that Heiko Oberdiek had already used the trick. :)
@StephanLehmke you could make ^^^^ work on classic tex most likely with some protected active definition that acted as a superscript in math or detected runs of ^^^^ otherwise
4:32 PM
@DavidCarlisle Maybe I was expressing myself unclearly. With the "Unicode based command syntax" I meant what \protected@write should write to files so it could be read as Unicode regardless what input encoding is active at the time of reading.
@DavidCarlisle Cool idea. Maybe a base for a modern reimplementation of inputenc ;-)
@StephanLehmke This is exactly what I proposed: they are active characters, so it may suffice to define them with \protected\def rather than \def.
@StephanLehmke as I say it would be easy to do, but as a matter of an interest what are you doing with the data read back, presumably not typesetting it otherwise the command forms would be fine.
But \protected@write can defeat everything. :)
@DavidCarlisle This would be way useful for the index! xindy can use UTF-8 and collating accordingly to any rule
4:53 PM
this seems to work for the 2byte utf8 range
\long\def \protected@write#1#2#3{%
it wrote
@egreg I’m testing the – very useful – regexpatch package. I’ve just noticed that \xpatchcmd expands the success argument if patching fails and both the success and the failure argument if the command to be patched is undefined.
@percusse: Fantastic answer on the \frownie question! :D May I suggest an addition? (Excuse my poor TikZ-fu)
\draw (0,0) node[ellipse,minimum height=0.4cm,minimum width=0.5cm,draw,rotate=120] {};
\node[fill,circle,inner sep=0.3pt] (left eye) at (155:0.8mm) {};
\node[fill,circle,inner sep=0.3pt] (right eye) at (45:1mm) {};
\draw (-125:1.5mm) -- (-20:1.8mm);
5:15 PM
Sorry, my family just arrived back from their trip; have to make lunch now...
@StephanLehmke make them a utf8 index instead, they will thank you for it
@StephanLehmke lunch?
@StefanKottwitz visiting the NAG Blog:-) (I guess that was you?)
5:33 PM
@mhp Thanks, I'll check into it.
@DavidCarlisle Yes, that was me, yesterday
I saw in the NAG blog the ISC '12 is in my hometown, 10 minutes away, in some days
6:00 PM
@mhp I seem to have found the mistake. Thanks again.
@PauloCereda Excuses no more! You are TikZ-able from now on, I'll ask @AndrewStacey for your TikZ-knighthood (now for just €99.95)!
I laughed and my girlfriend called all of us names. I apologize on behalf of her.
@percusse LOL We are the knights who say \ni. :P
@percusse I can use Paulo's credit card number directly; the €99.95 will arrive soon.
@egreg Ah thanks! Oh wait. :)
@PauloCereda I'm on the train with nothing to do, having fixed the bugs in regexpatch. :)
6:08 PM
@egreg Yay, I need about 120 more TikZ questions for getting my hands on that number :)
@percusse You can start with the unanswered list ;-)
@percusse Still 6000 rep missing? How can anyone not hit rep cap every day? It's easy!
@egreg Wow!
@MarcoDaniel Hahaha, everyday I try on a few but they are tough.
@egreg Simple answer -- the day isn't long enough ;-)
6:10 PM
@PauloCereda Train's arriving. It was a missing condition checking. :)
@egreg My rep cap is flexible. I can hit it with 60 sometimes :)
I let the crowd to decide when...
@egreg Still wow. :)
Is it time to close this one?
Q: Undefined \pgfsetpath: is tikz or Miktex update responsible

PerI run the following simple example using MikTeX 2.9 (complete installation) that is regularly updated (this is one of the first examples in TikZ manual): \documentclass{article} \usepackage{tikz} \usetikzlibrary{arrows,calc,intersections} \begin{document} \begin{tikzpicture} \path [name path=on...

6:29 PM
Mass/procession time! I'll be back later. :)
7:08 PM
@PauloCereda Wow - L3 and TikZ. I'm impressed.
7:32 PM
@StefanKottwitz: Interesting how my flag was "disputed" after you deleted the question as (most likely) not being an answer:
Not sure how the flagging works behind the scenes...
8:02 PM
@Werner I did not see a dispute. I noticed the flag, read the non-answer, converted it to a comment, that's all. I think the OP is still able to see Andrew's comment in his inbox, so I did not move Andrew's comment as it's only for the OP.
My "not-an-answer" flag was disputed. I did not dispute someone else's "not-an-answer" flag.
Either way I just found it strange that my flag was disputed, yet the flag was still honoured (and subsequently deleted).
@Werner Honor thy flag ! With or without consequences.... pulls the pin and hands it over
@percusse :)
8:21 PM
@PauloCereda Here it is:
scnr :)
@PatrickGundlach That's a terrible choice.
I would go for a lighter background color for better emphasis.
@percusse Perhaps white number on white shirt?
@PatrickGundlach Thanks to you my girlfriend has a different view on my activities here.... I regret nothing!
8:37 PM
@PatrickGundlach Happily Paulo is at the procession. :)
@PatrickGundlach My eyes!!!!
@egreg The procession ended earlier because of the rain. :)
@PauloCereda Oh! How was the procession? (Just trying to pile up some lines so the offending shirt will disappear: it's not striped!)
@egreg (Agreed!) Ah, the procession was very good, but the rain seemed not to stop. :)
I recorded the ornaments in front of the church, I'll upload the video for you too see. :)
I tried to record myself singing, but I almost lost the timing (it was in the eucharistic prayer, we were singing the answers). :P
@percusse There were other images returned from the "latex shirt" search, but I thought they were even more unsuitable for the chat.
@PatrickGundlach Do that and we will all go to Germany and kick you. <3
8:43 PM
(... doing google search right now, starting photoshop...)
@PatrickGundlach o.O
actually it is really funny to search with "safe search" off, the results are almost completely safe
Uh-oh. :)
Interesting! If I add this line: \index[ica]{\songindextitle@\songliturgy \songtitle} inside a command definition in my .sty file, I get an Undefined control sequence.. The line works outside. Any hints? :)
@PatrickGundlach Safer. :)
8:50 PM
@PauloCereda Better put a space before @: in a .sty file @ is a letter.
Thanks to Patrick <3 has a new meaning for me.... :P
Better, @PauloCereda?
@egreg Oops, I didn't know that. :) Thanks. :)
@PatrickGundlach ooh sexy! :)
@egreg: It worked! Grazie mille! I'd never find that. I thought it was some sort of scope limitation. :)
@PauloCereda The space in \songindextitle @ is ignored anyway. But without it you're specifying the \songindextitle@ control sequence (that's undefined). It doesn't happen in normal text because there @ is not a letter, so it stops the parsing of the control sequence name.
9:05 PM
@egreg Awesome, I'll never forget. :)
@egreg: I'm exporting the movie. :)
9:37 PM
@mhp Uploaded fixed version of regexpatch. Unfortunately it won't probably go in the DVD of TeX Live 2012. :( Thanks again.
@egreg: 34 minutes for Vimeo encode my video. :(
9:48 PM
Hi, everyone!
@GonzaloMedina Hi Gonzalo!
How are you?
@PauloCereda Fine. You?
Can somebody please have a look at this code?
@GonzaloMedina Fine. :)

morekeywords= {},
otherkeywords={$,\{ ,\} , [ , ] },



Commenting out the line morekeywords={}, the code produces an error. This seems like a bug to me... or perhaps I am missing something?
@GonzaloMedina Maybe we can't have other keywords without more keywords. :)
10:02 PM
@PauloCereda Well, but there really are no more keywords in my example, and if that's the case, I didn't find a mention about it in the documentation. As far as I understand, otherkeywords handles characters considered to be of type "other" according to the listings classification.
@GonzaloMedina Indeed. I understood the same from the documentation.
@PauloCereda However, you seem to be right...
@GonzaloMedina It's a funny behaviour. :)
10:17 PM
@egreg: vimeo.com/43634667 Password: texsx
@PauloCereda Very nice decorations. In the first painting there was "the rock"!
@egreg The very same! :)
@PauloCereda How's it called? The one near Canossa is called "Pietra Bismantova".
This year, both gardens were merged, so the street in front of the church doesn't exist anymore. :)
@egreg We have two nearby. :) The one from the decoration is the "Morro do Cuscuzeiro". We also have another one called "Morro do Camelo". Cuscuzeiro is named after the "cuscuz" plate (they usually have that shape!). :) The other one is called Camelo (camel) because it reminds of a camel. :)
10:35 PM
Two votes for closing
Q: latex: Undefined control sequnce

thetnaFor the following piece of LaTeX code, {\hat \theta} = { \argmin_{\theta \in \Theta}} I got following error: undefined control sequence={\argmin How would I correct it?

@egreg One from me. Voted. :)
@PauloCereda Peculiar. Weren't for the vegetation they would remind the Monument Valley in Arizona (and in John Ford's movies).
@egreg True. :)
11:05 PM
Hey, just dropping a note that Stack Overflow's migration path list now includes TeX.SE; that means that those of you who patrol SO looking for questions that need to be migrated can now either vote yourself or use a standard off-topic flag which 10k users there can review.
It's the same amount of work for you and less for us poor overworked SO mods. :)
@mmyers Thanks. :)
No problem. And with that, I'm out, and you'll probably never see me in here again. tips cap
@mmyers Learn TeX and join the fun. :)
@PauloCereda 95000 by tomorrow. @Werner is going to lose his bet. :)
@egreg Yay! The countdown is now open! :D
11:13 PM
@egreg I think some bounties may have tipped things in your favour. That and the fact that your answers are correct... mostly. :)
@Werner My total earned bounties is 1225; 400 in 2012. Don't look for excuses. :)
@egreg Darnit... <he does his research as well>.
so do I get a tikz gold badge now?
@DavidCarlisle You'll be \missing that goldness for a while, sorry.
@DavidCarlisle Very clever.
11:20 PM
@DavidCarlisle Well I think that means you have to answer with tikz and not use the old picture environment.
I wonder how long I can answer tikz questions just by running the MWE with \tracingall and inserting an expandafter or two and not actually knowing what any of the code does:-)
@DavidCarlisle LOL
@DavidCarlisle Welcome to my TikZ badge...!
Gotta love some obscure parts of my code:
@DavidCarlisle You're on the right path: you need only 194 more answers in for getting the gold badge. :)
11:40 PM
@egreg actually it's more fun dismantling multicol columns with \lastbox:-)
@DavidCarlisle Try with \index{...} inside it. :P
There was a question about using verse in a footnote, people want to put everything everywhere.
@egreg I was gonna link that question here. :)
Follow-up: how to put a mini-TOC in the footnote.
@PauloCereda A longtable too.
@egreg Yay! :D
@PauloCereda With some nested footnotes.
After this it's better to go to bed. :)
11:54 PM
@egreg Buonanotte! :)
@PauloCereda hehe I like this... ;-)
@GonzaloMedina Don't you dare! :)
@PauloCereda I see ToC and I can't help it... I must provide the code ;-)
You know, I suffer from TOC with ToCs.
@GonzaloMedina Go ahead! Now I'm curious! :P
@GonzaloMedina And I with indexes (indices?!).
@egreg well it's OK so long as the \index is in hmode isn't it? If you put a write node into the vertical list it dies of course.

« first day (585 days earlier)      last day (4007 days later) »