A well designed package must be extendable. It will be similar to the concept of moderncv. So I do only a base layout, which can easily be replaced by custom ones. The point Ulrike mentioned is correct, but this is - as I think - more acceptable than putting a ifundefined around every item. If I can do it, the way I intend this, every school boy can design his own layout. — MaestroGlanzyesterday
@Johannes_B Indeed, a custom design would be in error suppress mode like \renewcommand{\design}{\titelnummer \titel \hfill \autor}. Any non existing wouldn't be printed. So a typo just leads to no output of this macro. This would be common with all used songs (this is for songs), so this would be an apparent error. If I do it without it, I either have to define a list of standard meta data (which I will probably do for other reasons) or define a "securing" macro which leads
to \renewcommand{\design}{\sec{\titelnummer} \sec{\titel} \hfill \sec{\autor}}
For an end user, who is not that much tex safe, the first version is much more convenient. - So: seriuosly
@MaestroGlanz moderncv is a very fixed and non-extendable class. As Ulrike noted, biblatex deals with defined/set fields in a bit more elegant way than all the CV classes out there try to do.
Designing a layout is a complex thing. That's why there are graphics designers and layouters all there who get paid for it. Every schoolboy should not be able to do that.
@Johannes_B Just the mechanism should work like moderncv. So the structure should be similar. I had a look into moderncv and it isnt that complicated. If you stick to the way the other styles are done, this can be done. Not by a schoolboy, but done. A color scheme in moderncv can easily be done.
I know what I want. You highly doubt that. My next approach will be converting errors to warnings. I read about that in the texbook (? or elsewhere). This might generate a lot of warnings, but would work. Constraint is, that it is only locally changed to a warning.
@MaestroGlanz there is really no need to design it so the users are expected to generate errors, so no need to use error suppression. When programming in any language it is best (and least confusing for users) if you use that language idioms, and no documents run with errors turned off
@MaestroGlanz you can easily do that for package errors, but for primitive tex errors such as undefined command there is no mechanism for that, the nearest is \scrollmode as I put in my answer
@cfr this is a disaster, we already had too many green squares, and too many ducks, and now we have a duck in a green square :(
@egreg Same here but I was not sure it helped with the matter at hand: perhaps I'll add it later (going out in a second). [I use \showtokens{#1:::#2} normally :-)]
I never liked templates, they make me feel... restrained. Constricted in a very narrow path. I always grab code from here and there and make my own document exactly like @DavidCarlisle suggested.
@Alenanno Even if a question might be duplicate, this doesn't mean that the answers are quite similar (or dupes.) In this case, the effort of the answerer should be honored in any case
singing: Ich schieß den Hirsch im wilden Forst, im tiefen Wald das Reh (dadadadaa); den Adler auf der Klippe Horst, die Ente auf dem See; Kein Ort der Schutz gewähren kann, wo meine Büchse zielt.
Hello! I don't want to be the bear of bad news, but I am not sure your entry is valid, as we asked for users registered at least on March 1. Your TeX.sx profile says you have 43 days in here... Maybe you could wait for the next contest... :( — Paulo Cereda2 mins ago
If you ring a bell and nothing happens, there might be two different reasons: Nobody is at home. Nobody wants to open the door. There is absolutely no (NO) use in ringing the door bell for a straight minute.
If you are worried that the person is hurt, stop ringi the freacking door bell and call the police/fire department or break in.
@JosephWright -- i can cope with \tracingall with plain tex, but latex adds so many layers that the buffer for my screen is soon overloaded, and i have to go to the log anyhow. i really wish there were some simple ways to say (in the middle of an "uninteresting" command expansion) that "i don't want to look at this right now; please shut up, just until this command is completed." without having to redefine the command in question.
@JosephWright -- no, but i do have some sympathy for his position. when i am tackling the debugging of a gone-crazy equation number that depends on being within a chapter and section, even a minimal example puts out more lines than my screen buffer will let me see. so i have to edit the log to get rid of the unnecessary stuff. (and that's a relatively simple example. never mind when an author has gone crazy with self-defined alternatives.)
@barbarabeeton As we all know, the nature of TeX means that any abstraction at all means long traces
@barbarabeeton The problem with measuring code by number of lines in the trace is that it means all users have to be coding experts, and that each problem has to be solved with a custom solution
@JosephWright -- last week, it took me over four hours to figure out what an author had done, that was solved by addition of one \end{list}! (she was using \def\xxx and \def\endxxx rather than nicely using \newenvironment. the concept was actually a rather good one, but the execution was dreadful.)
@JosephWright -- someday i may look at that, but for the present, there's no way it can be adopted at ams. we need stability and predictability. this is not the same as stasis, of which we are often accused (sometimes even by me).
@barbarabeeton What about a command defined by \DeclareRobustCommand{\foo}[1][a]{#1}? In order to see what \foo really does you need \expandafter\show\csname\string\foo\space\endcsname
@barbarabeeton But with \xshowcmd from xpatch you just need \xshowcmd\foo. ;-)
@barbarabeeton Oh certainly. I was thinking more that new code just for LuaTeX will often be \def\somecmd#1{\directlua{some.function(#1)} so not much shows
@JosephWright well, many languages allow you to linearize the program run in a debug mode... It quite depends on the debugger as well (remember that e.g. in C++, the compiler only includes the debug metadata, and you have a variety of debuggers at hand)
@yo' I suspect that most programmers don't expect to track every function's definition through in the way we do: I really don't know how they do debugging :)
@PauloCereda I am, alas, a most humble low-rep user and TeX wannabe who has nonetheless developed a hankering for a duck. (Or hand-puppet equivalent.) I cannot edit the punch card, though! :( If I put in an entry, could you punch the card for me? I live in hope....
@yo' I guess: for most 'core' programmers in the TeX world I guess there is an assumption that familiarity will extend to basically 'all of the running code' (i.e. that @DavidCarlisle or @egreg or Frank or Petr or ... could write an entire format from scratch if required)
@JosephWright It depends on how much the programmer knows the inner workings of the language. :) I use a couple of libraries myself and I usually track the error stack until to the triggering point. :)
@DavidCarlisle Along with the high reps and unusually friendly atmosphere, there also seems to be a large number of those auto-generated "gravatars". Strikes me as an odd combination, actually!
@notorious Or, with \usepackage{siunitx}, you can simply do \num{8.4e23}
@notorious And, with the same package, you can type If \num{8.4e23} helium atoms, traveling at a speed of \SI{6500}{m/s}, perpendicularly collide with a \SI{0.5}{m^2} wall every \(2\)~seconds, calculate the pressure
@notorious In the document preamble, that is, before \begin{document}
\documentclass{article}
\usepackage{siunitx}
\begin{document}
If \num{8.4e23} helium atoms, traveling at a speed of \SI{6500}{m/s},
perpendicularly collide with a \SI{0.5}{m^2} wall every \(2\)~seconds,
calculate the pressure
\end{document}
@JosephWright of course even if mathjax re-fix it, if it stays in their contributed extension area it doesn't help on the stackexchange network, unless SE incorporate it into the config they use.
@StrongBad although you could query ctan if the catalogue entry is correct as the full text of the licence on the file is % This file has no restrictions on its use, distribution, or sale.
@JosephWright that did occur to me, but it's not very different (and less restrictive) to the comments on tex it would also allow someone to re-submit to ctan with any licence they wanted, as there is no living maintainer that's all there is
@JosephWright Sometimes I hate Debian. I can see their point about only wanting "free" software, but the only way I can interpert that line is that the package is free.
@DavidCarlisle Are you sure those are ducks? They look very much like geese .... I'm afraid they are not covered by my society. Petty, perhaps, but I have a long-standing grudge.