@Gigili I would do a full one, but the point here is that gets downloaded by the installer as it runs. You only need to manually get the 'stub' that does the work.
@PauloCereda anyway the gif was called "duck-says-no" before it was uploaded:-) Others you could use: http://www.animationlibrary.com/sc/141/Ducks_and_Geese/?page=2
I'm guessing from your reaction that that is a no.
@FaheemMitha yes I know that's what the system told me I just couldn't connect any of the words in your comment to what I wrote (which was just for once a direct statement, not a reference to anything)
@JosephWright trying to install the pretest again...
@JosephWright Mr. Joseph Wright, sorry I just saw your response for chat. What workflow solution do you normally use for chemistry publication in which you would need chemical compound labeling? (Even if not submitting to the arXiv, I'm still concerned about the security risk with -shell-escape)
I'd like to define a new type of operators, which would be the same as the usual ones I define using \DeclareMathOperator, but with a different font.
I tried searching the site for some guidance on how to do this, but was unable to find anything that seemed to apply. Anyone have any idea how to do this/where to find instructions?
@DavidCarlisle That'd indeed be one way of doing it. I somehow thought it'd be nicer to define a new "class" of operators---but maybe that's just overdoing it. Do you think so?
(I'm doing this because I'd like to use a different font for categories)
@Danu what do you mean by "for categories" do you mean the names of specific categories, or the names of elements of a category or of the functors or....
The names of categories, like Top or K-Vect, etc. I plan on using math operators for the objects (\operatorname{Ob}) and the morphisms (\operatorname{Mor})
@Danu I meant things such as Top, but Ob and Mor are operators. Something like K-Vect needs special care, however. Probably I'd define \newcommand{\Vect}[1]{#1{\operatorname{\mathbf{-Vect}}}} using the features of \operatorname for getting a hyphen rather than a minus sign. Then you'd say \Vect{K}
@Danu First of all, define an abstract command: \newcommand{\category}[1]{\mathbf{#1}} and then do \newcommand{\Top}{\category{Top}} for the names you use more frequently or that, like K-Vect need some special treatment. Here \mathbf is just a stub, you can change it at any time so ensuring uniformity.
@Danu So the code above would become \newcommand{\Vect}[1]{#1{\operatorname{\category{-Vect}}}}
I do pity those of you from other countries, not having the BBC to have that public service investigative journalism that answers the important issues of the day: bbc.co.uk/guides/z8jcwxs
@ChristianHupfer oh join the queue that gets the bus from London to Oxford, spend an hour in Oxford, get the bus to Cambridge, spend an hour in Cambridge, get the bus to London, get the bus to Heathrow and be out of the country in a couple of days, having seen all the main bits. There are buses for all legs of that journey running every ten minutes or so....
@DavidCarlisle Well, I have been in Cambridge already 12 years ago, I think King's Chapel is still there, as well Trinity College or John's College etc and the Cam river and the bridges ;-)
@ChristianHupfer oh in that case that box is already ticked so you just need to do London<->Oxford not the usual triangle so you can be in and out the country in a day:-)
@FaheemMitha one main branch split down it's full length, in the picture below you see the whole horizontal part above my car split off the bright orange wood going vertically up the tree. Willow's are prone to spltting:-) https://goo.gl/photos/KaxWNk8irfipTFUR6
@DavidCarlisle @barbarabeeton @DavidCarlisle: amsgen.sty redefines \@ifstar, and this breaks some tests in the KOMA-classes (see tex.stackexchange.com/questions/303623/…). Do someone knows what is the rationale behind the redefinition?
@UlrikeFischer -- i think @david and @joseph have got the underlying reason it's defined. as far as i can tell, it was included in the original translation from ams-tex. recognizing a space that intervenes between \\ and a [ is very important; not so clear about the * but plausible. i'm putting this on the list of things that need to be considered when amsmath is overhauled (since i haven't yet turned the list over to @david).
@DavidCarlisle The sty contains a \new@ifnextchar, I wonder why it then didn't define a \new@ifstar ... it is a bit unfortunate when a package modifies such a kernel command.
@barbarabeeton Yes, that's my feeling too. AS I say, for 2e this is 'fixed' but I want to tackle the team yet again about xparse and whether our current approach there is right
@barbarabeeton @JosephWright @DavidCarlisle: Yes, I think the spaces are important. If I do \def\@ifstar{\peek_charcode_remove:NTF*} the test from KOMA still fails, but with \def\@ifstar{\peek_charcode_remove_ignore_spaces:NTF*} they work again. But I'm not sure what KOMA can do -- probably will need to save the original definition.
I have been using the Logicproof package to write proofs in Fitch style. It creates environments using tabular to make writing proofs less bothersome.
I can't seem to figure out how to create a dashed box in a subproof as in this example:
This is what I have so far. The second subproof should...
@UlrikeFischer possibly although it's only a trivial wrapper around ifnextchar so you could just use \kernel@ifnextchar*{...}{...} in places where it matters.
I have been using the Logicproof package to write proofs in Fitch style. It creates environments using tabular to make writing proofs less bothersome.
I can't seem to figure out how to create a dashed box in a subproof as in this example:
This is what I have so far. The second subproof should...
