@Kurt It's not his day. ;)

@Qrrbrbirlbel Well, now is a new day ...

@Kurt bad habit to get in to, you could end up being like @egreg

@DavidCarlisle LOL, I think not. @egreg and you knew mutch more about TeX/LaTeX than I. I think I was lucky ...

D'oh: sourceforge.net/p/pgf/bugs/259

@AndrewStacey :-)

@percusse Fortunately, when I originally posted that "bug" (to pgf-users) then I also posted another oddity which did turn out to be a genuine bug. So my initial contact with Till Tantau is a score draw, I deem.

@AndrewStacey He is quite hyped about fixing bugs/closing tickets lately, so I'm sure he is happy anyway.

@percusse I can't think of a way to do it directly in TeX, but the tables could be stored in SQL and use datatooltk to pull the sorted data into a datatool file.

@Dan Try texdoc glossaries-user or texdoc glossariesbegin or look at the glossaries samples directory or try the article on the LaTeX community site. You don't need Perl to uses glossaries you can use makeindex directly.

@DavidCarlisle I call upon your expertise to answer the latest comment on my answer tex.stackexchange.com/a/129521/86

@AndrewStacey That's not funny

@AndrewStacey we should get some l3 regex submitted to the syntax highlighter for this site (which uses some google api if I recall correctly)

@DavidCarlisle code.google.com/p/google-code-prettify

@PauloCereda When you have finished answering @AndrewStacey's question above you can submit some syntax rules there, now you've found it:-)

@DavidCarlisle A vim style? No thanks. :)

@NicolaTalbot thanks! that was very helpful!

@DavidCarlisle Damn, even on Lua questions you are faster than me!

@JosephWright oh I know lots about lua:-)

@DavidCarlisle: can I suggest an improvement to your answer? :)

I was gonna answer it, but you were faster. :)

@JosephWright Actually I'm on the lookout for tikz questions (that @Qrrbrbirlbel doesn't get to first) as I only need half a dozen more to get a silver badge will probably do for my new year's resolution

@PauloCereda edit away:-)

@PauloCereda I think I'd say you shouldn't coerce here: non-numerical argument = error

@JosephWright Good point. :)

@JosephWright Is it ok to make a feature request for one of your package using this chat room?

Just for fun:

@JosephWright: assert(type(#1) == "number", "we need numbers!") :)

@PauloCereda OK, you could of course do that, but how far do you go?

@Philipp Yes

@JosephWright Not that far. :)

I expect some witty answer from @DavidCarlisle.

@JosephWright: what's your Mac wallpaper?

@JosephWright In this answer (tex.stackexchange.com/a/130300/6870) to my question about "related entries" in BibLaTeX the issue of mutually relating references came up which leads to a LaTeX overflow when used with biblatex-chem but is ok with standard styles since built-in biblatex styles have the ability to detect related entry loops. Could you add this functionality to biblatex-chem as well, please?

@Philipp I can certainly look at it: probably the weekend

@JosephWright Mac wallpaper, please. :) Tell me it's an epic HD wallpaper. :P

@JosephWright Thanks, that's great.

@PauloCereda Maybe it is even this one (concertposter.org/-2013Mar/Epic/Epic-Hero-Over-Drop.jpg) :)

@Philipp in 3D! :P

I have a bunch of wallpapers, transitioning every 15 minutes.

@JosephWright: ^^ :P

@PauloCereda Even more epic then ;)

@DavidCarlisle's wallpaper:

@PauloCereda And this one for bad days when you simply want to get in an angry mood :)

:10982601 $ vim
bash: vim: command not found

@DavidCarlisle <3

@Philipp C-x wallpaper :)

@PauloCereda I voted for "Leave Open", by the way. (There is one close vote for "primarily opinion-based".)

@Qrrbrbirlbel Is there a "leave open" option?! Oh my. :)

I need more rep. :)

@PauloCereda In the Review section, yes.

@Qrrbrbirlbel Ah review. :)

@PauloCereda ... and one vote closer to the next badge. ;)

Maybe @David can teach me how to harvest rep by adding % to the end of some line. :)

@Qrrbrbirlbel ooh! :)

@PauloCereda That's egreg's speciality 2000 bonus hrmph.

@DavidCarlisle :)

vimeo.com/73190737

@PauloCereda not very witty I fear

@PauloCereda ?

@DavidCarlisle Nice answer. :) I'll upvote it ASAP. :)

@DavidCarlisle A font which incorporates Braille in the typeface. :) Not my cup of tea, but a nice idea. :)

@PauloCereda yes I just wondered how you found the video or if you helped set it up or...

@DavidCarlisle Ah I saw it in a Gizmodo post on my RSS reader. :)

Gotta love barbara's comment. :)

Hello

@leo Hi

What are you studying?

Right now, Galois theory

:-)

Well, I'm not studying right now. I'm taking that course

I need to do my first script

Where can I learn?

I think it must be in Perl or Python

@leo I'm touring with my bike. ;-) Today a climb to a 1460m high mountain in the Apennines, with a magnificent view over the “pianura padana” (the Po river plain).

@leo Ask @PauloCereda

@egreg Here I am. :)

@leo Tell me about your script. :)

@egreg Cool!!! You are a fortunate man! Could you share a photo? :-)

@leo Here's the view (but taken in the winter)

@Paulo Hi! I' ve never done a script. Now I must translate some question in a tex file to GIFT format in order to use them in Moodle

@leo In a clear day like that you can see a large part of the Alps

@leo Hm I see. :) Do you know if the standalone class can help you?

So I wanted to automate the process and learn scripting :-)

@leo: which OS do you use? :)

@egreg It looks very nice indeed. It makes me wish to be there

@PauloCereda Windows, but I'm have been trying Ubuntu for about 3 months

@leo There are too many pylons, unfortunately, because of the mountain's very good position.

@PauloCereda Did you interpreted GIFT as GIF? I ask because the class you suggest is useful to produce images

@leo Yep, I thought it was GIF. :) Isn't it? :)

aaaaaaaaah it is a Moodle format.

My bad.

@PauloCereda Indeed ! :) I was looking for a link to the explanation

a question in that format will look like

Enunciado de la Pregunta.
{
= Opción 1. Respuesta Correcta.
~ Opción 2. Respuesta Incorrecta.
.
.
.
~ Opción n. Respuesta Incorrecta.
}

there are some guys who made a little program tex2Gift, but it seems is not available

they are from the Universidad Nacional de Colombia

namely: funlam.edu.co/lampsakos/n6/a5.pdf

@leo: in that case, I think Python might be very useful for you. :) The question now is, we might need to have some specs in order to read the .tex file and say, "hey, this line is the question, the next one is the answer..." and so on. :)

@egreg We are plenty of those these days

@leo: see Code 4 of the paper you linked. :) We might need something like that: the specs on which our script will parse the .tex file. :)

Thankfully my Spanish is not so rusty. :)

@PauloCereda exactly. I think the question can be enclosed by a question environment. The choices by choices environment (inside the question) which behaves just like an enumerate. Instead of \item a \choice, and a \correct command to mark the right choice. What do you mean by specs?

@leo The semantics of your document. :)

This thingy you just said. :)

@PauloCereda I've hear that it's easier to someone who speak portuguese to understand spanish, than the other way around

@PauloCereda Oh I see. :)

@PauloCereda well the exam document class have exactly those commands

@leo Once you define how your .tex file will be, the GIFT generation is not that complicated. :)

@PauloCereda It seems the way to is by using the exam document class. That way we can do things like:

\begin{questions}
\question One of these things is not like the others; one of these
things is not the same. Which one is different?
\begin{oneparchoices}
\choice John
\choice Paul
\choice George
\choice Ringo
\CorrectChoice Socrates
\end{oneparchoices}
\end{questions}

And the algorithm in the paper I linked can be simplified. It will no longer need to know how many questions are there. The loop will stop when it reach \end{questions}

why print "Mary had a little lamb," gives Syntax error in Python IDLE?

@leo But not in regular python. (I have no idea; I've never used IDLE.)

Look at:

G:\Documents and Settings\Leo\Escritorio>python mary.py
  File "mary.py", line 2
    print "Mary had a little lamb,"
                                  ^
SyntaxError: invalid syntax

G:\Documents and Settings\Leo\Escritorio>

that was the output of in the terminal

:-(

@leo Does print("stuff") work?

@Qrrbrbirlbel yes

I'm just coping and pasting from a tutorial

@leo That's what I did. ;)

searched Wikipedia for IDLE and Python, found a link to an guide

and scrolled until I found print

@leo Could it be another case of the wrong quotation marks?

(I.e. in the guide it has 'smart' quotes.)

@Qrrbrbirlbel I'm following this one

@leo I've found this: annedawson.net/Python_Editor_IDLE.htm

@AlanMunn nope. It has "

@leo Yes, I just looked at your guide.

@leo: print "xxx" raises an error in the new 3.x series of Python (it's valid for 2.x though), maybe that's why.

Being print a function, they decided to require parentheses. :)

Can somebody recommend a guide to writing packages? (No, I don't want to deal with .dtx files.)

Or should I?

@Qrrbrbirlbel dtx files are just packages where the comments are latex markup rather than plain text, so they make for nicer documentation

@DavidCarlisle I am currently reading the chapter "Dokumentieren eigener LaTeX-Pakete" (the last one before the appendix) from the Companion ...

@Qrrbrbirlbel reading German is a lot harder than writing a package

@DavidCarlisle really? :-)

@PauloCereda that explains everything. It must be an old tutorial

@DavidCarlisle Haha ... it shouldn't be too hard to transfer one's .sty to a proper documented package? Saves me the hassle if it won't be accepted (or it doesn't work at all).

@Qrrbrbirlbel I always start undocumented, then once it's more or less working just use an editor to add the % \begin{macrocode} lines at all the main gaps then get round to adding some words.

@DavidCarlisle That's what I thought.

@Qrrbrbirlbel texdoc clsguide dtxtut dtxgallery docstrip

@texenthusiast I liked David's response more ...

@Qrrbrbirlbel from the horse mouth :)

@Qrrbrbirlbel Write code first, document it later. :)

And remember: there are no bugs, only random undocumented features. :)

@PauloCereda All of my code's features are undocumented ...

@Qrrbrbirlbel I know that feeling. :)