Re: [Groff] Macro arguments question

2005-11-14 Thread Tadziu Hoffmann
Ah, and I forgot to emphasize that one of the most important aspects of environments is that the current "partially collected line" is part of the environment. Using environments, you can collect and format several different "threads" in parallel. __

Re: [Groff] Macro arguments question

2005-11-14 Thread Tadziu Hoffmann
Just wanted to clarify a few things about environments. The idea of environments is to define several different "parameter sets" for formatting, with the purpose of being able to easily switch between them (e.g., one environment for the normal body text, one for footnotes, etc.), and to be able t

Re: [Groff] Macro arguments question

2005-11-14 Thread Tadziu Hoffmann
> > But this is a consequence of wrapping it in \{...\}, so if > > you just remove the quotes from your argument it comes out > > right. No, this interpretation appears to be incorrect. The \{...\} is at best ineffective here. You can see this if you define the macro as follows: .de temp # arg

Re: [Groff] Macro arguments question

2005-11-13 Thread Clarke Echols
Ted, DUH! :-) Thanks. I tried my idea after I posted my thinking, and found what you did: Escaping end-of-line with quotes around the entire thing does work as intended, but I have to pay attention to breaks, and using \{-\} pairs keeps the quotes. However, your suggested method works as I int

RE: [Groff] Macro arguments question

2005-11-13 Thread Ted Harding
On 13-Nov-05 Clarke Echols wrote: > One thing I *really* like about groff vs troff/ditroff is the > expansion of macro and other entity names beyond two characters. > Nice job! > > I am considering using macros to solve a problem that would be better > if handled in a database, but I don't want to