@Anthony well, a macro implicitly grabs for the argument the first following token. If this token happens to be a {, it grabs the whole group. If it's a }, it gives an error.
Thanks @yo'. I can't seem to get my documentclass to work.... I'm doing \documentclass[]{C:\Users\polloreno\Desktop\Notes} but it's saying it doesn't recognize it...
"Undefined control sequence". Is that in the document class I made then?
I know how to define a package - but how do I make it available (to myself) at all times?
Say I have the package file commonstuff.sty, that I want to be able to include in any .tex file I create on my computer. Where do I put it? Do I need to run some installer on it, or is it enough to keep it ...
Haha. Thanks. I found the folder with the article.cls, I'm going to see if that works. I think I might try reinstalling things later, I installed with texmaker and my whole setup is weird.
Well, you should use proper structure, putting it with the disto-installed packages is not that.
But it'll work, as long as you don't re-install anything. On the other hand, it's theoretically possible that your distro will delete the file at some moment.
I am about to write my thesis on Texmaker but frankly I am a quite clueless tex-virgin.
I would like to use the document class of our university but I couldn't figure out how I can import the files to Texmaker. Does anyone know how to do this?
FYI: There is a bitex, a src, a lyx and a src folde...
@JosephWright I started to put some words into latexrelease.dtx, also if (when?:-) code is finalised I hope to do a "long lines" pass over ltoutput and ltfloat, it's not exactly a good example of avoiding over full hbox at present...
Whoops, another problem. I read that I should use `\renewcommand*\ttdefault{txtt}` `\renewcommand*\familydefault{\ttdefault}` %% Only if the base font of the document is to be typewriter style
@yo' I don't think there is anything to change in the format, the format doesn't support keyval options in class or package. A package that is adding keyval class and package options could redefine it if it felt brave enough.
@yo' it (me, as it happens) remmoves all spaces (and braces as a side effect0 one of teh first changes we did for 2e. As I say any class that is adding keyval class options can redefine \@onefilewithoptions to do something else.
@DavidCarlisle and I ask whether \documentclass could be modified to have no other effect but creating a macro (with whatever crazy name that nobody uses) that would grab the optional argument as is, before doing anything else. This would be enough
@Anthony the right package seems to be newtx. However, where have you got that infromation from?
@yo' in latex2.09 if you went \documentclass[oneside, fleqn]{article} you would get an error for unknown option ` fleqn` this was just about number 1 FAQ, so allowing white space after commas was high priority, and we didn't have much memory to spare for full parsing, so. spaces just went. the more careful space hanfling in keyval came a year later
@DavidCarlisle I know there were these problems. I just ask whether there's a technical limitaion why it can't be added now, without affecting anything else
\documentclass{article}
\renewcommand*\ttdefault{txtt}
\renewcommand*\familydefault{\ttdefault} %% Only if the base font of the document is to be typewriter style
\usepackage[T1]{fontenc}
\begin{document}
Hello, World!
\end{document}
@JosephWright i wouldn't change any of that but if the original optional arguments were dumped somewhere it would be easier for a package to do its own thing
@yo' there are always downsides to adding anything though it just increases the chance that documents woke in one place and fail with weird errors elsewhere
@Anthony that's what happens if you do not have fints installed tex goes back to its rouots and tries to run metafont to make them, it doesn't work but it shouldn't have tried, you can't use fonts you haven't got installed
@Anthony I mean in the document. Because this suggests that you have a typo there. Your LaTeX tries to get the font xtt, which doesn't exist. The name is txtt
@Anthony ah damn, then I duno :-/ and I don't run miktex (not even windoze), so I don't think I can help with that one...
@DavidCarlisle I'm just making a suggestion. I'm far from knowing all the pros and cons. I see one pros (allow mykey={foo, bar}) and no direct cons (unless some package uses a macro called myclass.cls@optarg@dump)
@JosephWright got to the end and it seems to have made a zip, but I'm sure I saw a "Failure skipping" message go past at one point, I'm running it again under script to hang on to the terminal output)
@Anthony I think that's the currently recommended way to use the newtx fonts in text and math
The txfonts package uses fonts that have many small (and some big) defects. Thus using newtx is surely better. However, these fonts don't have a "Small Caps Italic" variant.
You could use the times-itsc font, but beware that they are really a poor version, as they are obtained by scaling the upp...
I mean, it's good to keep to the layout that the class owner expects. But other than that, it's just a bunch of formatting macros, and you can make such a things yourself. People will say that it's not "separating style from contents", but for a thing used once in the document? Who cares.
@StefanKottwitz Your decision. I would delete all opinion based comments that don't add anything useful for the OP. golatex.de/viewtopic,p,68034.html#68034 I thought my och Leute would be enough to state my disagreement with opinion-ping-pong.
Hi all. openSUSE will have it's conference between May 1-4 in The Hague, Netherlands. If you want to participate, do some cross pollinating and hack with us, we would love to have you attend - bit.ly/1yeBGg0 Cya at FOSDEM and come enjoy one of our openSUSE beers while you're there.
See some of you at SCALE
Cheers
Doug
_______________________________________________
devel-announce mailing list
devel-announce@lists.fedoraproject.org
@JosephWright I may have something local... they all work when I run them by hand but the config used to pull in the hyperref etc is failing somewhere, oh could it be because Ive run by hand and have non-hyperref aux files somewheer? I'll try to do a make clean first
@PauloCereda I'm looking into something portable. After my disappointment with Korg KROME, I realize that I won't make it in lower-mid class. Now this cought my attention:
@yo' I once had the chance of playing with some digital piano acting as a controller to a Roland Juno. It's an incredible synth and I think it might cover at least a lot (but maybe not all) of what Jupiter offers.
@DavidCarlisle I sent him a PM suggesting to look for a local user group two weeks ago. Also gave a name for the country from which he is posting. Never replied.
@PauloCereda well, what I need is something I can carry with me twice a week downtown and back, and what does a good job on stage (where I can carry more if I want, of course, to make things better)
What I did was copying the original beamerouterthemedefault.sty in my working directory and modifying that single line to make the frametitle uppercase. It's working fine, but is there a more efficient way to get the same result?
honestly, Korg KROME 73 was going to be it, before I got to touch the keybed :( As one friend in Sound.SE put it: So it's a nice keyboard unless you have to play it? :(
@DavidCarlisle Thanks, but I can't use that here - I think it is only for processing arguments, whereas I need to process something which is the result of running set-keys on an argument...
@cfr you can always pass the value you have to a helper function that split sits argument although as Joseph said it's always going to be quicker to use a single primitive def
Well, I was trying not to, but then people seem to be saying it would be better to just use \def. So I'm confused. In general, the answer is: I wanted to use the keys processing stuff to update a command to handle more than 9 bits of things. So I started with a file which used a mix of \def, \newcommand, \NewDocumentCommand but no expl3 at all. Once I added the keys stuff, obviously I added expl3 syntax to the mix. So I was trying to clean it up slightly by moving more of it to expl3. Hence, originally I asked if there was something expl3-ish to replace \def\lc@awdur#1-#2\@nil{#1}. And @yo'…
@egreg So the contrast is \seq_set_split:Nnn versus \seq_set_split:NnV? I don't understand about w yet. (Or \q_stop.) In one case I currently have \seq_set_split:Nnn and in one \seq_set_split:NnV. So the V should become a w?
Is anybody else having trouble with CTAN? If I search for 'glossaries', I get:
The search found no matching documents on CTAN in 2s37ms.
Consider to reformulate your query for better results.
Format version is not supported (resource: ChecksumIndexInput(MMapIndexInput(path="/serv/www/www.ctan.org/index/pkg/segments_14dlu"))): 1071082519 (needs to be between -1 and -11). This version of Lucene only supports indexes created with release 1.9 and later.
@cfr It depends on how you want to use the thing. With the sequence approach you trim spaces at either end, for instance, at the expense of expandability.
@egreg @DavidCarlisle What I meant is, why that rather than \seq_set_split:NnV? That is, I said I had that and egreg said either \seq_set_split:Nnn or the weird thing, but I don't understand why the weird thing rather than \seq_set_split:NnV.
@cfr because they think too complex. My opinion is: whatever sounds reasonable and works well. Splitting a string by -, taking the first bit apart and then joining again is something I've done before in many languages, so why not L3.
I am about to write my thesis on Texmaker but frankly I am a quite clueless tex-virgin.
I would like to use the document class of our university but I couldn't figure out how I can import the files to Texmaker. Does anyone know how to do this?
FYI: There is a bitex, a src, a lyx and a src folde...
