Re: [9fans] troff macros for typesetting books/longer texts
I really like the GNU project's Texinfo markup language, which sets on top of TeX, but you don't have to know TeX. (I've been using Texinfo for 20 years, but don't know any TeX.) I've written books in troff, Docbook/XML, and Texinfo, and Texinfo is by far the easiest. HTH, Arnold In article aanlktinh0btuvfzw-yqmvy-zvaouuo-4gyoj0kvom...@mail.gmail.com you write: hello html? For those who use math in their docs, this might be of interest: http://www.mathjax.org, gabi On Thu, Mar 24, 2011 at 2:16 PM, hiro 23h...@googlemail.com wrote: i think everybody would appreciate one xor the other cleaned up, de-pccified and added to the distribution. I like this use of languages :) The thread is getting big. Perhaps simply learning troff/tex is indeed easier. But I really am no typesetter, just a simple computer user. Tex is yet an other language, Latex too complicated, Microsoft Word too ugly, Troff macros not in a good state... What can I use? -- Aharon (Arnold) Robbins arnold AT skeeve DOT com P.O. Box 354Home Phone: +972 8 979-0381 Nof Ayalon Cell Phone: +972 50 729-7545 D.N. Shimshon 99785 ISRAEL
Re: [9fans] how can I set path
I'm new to plan9. i don't know how to set path on plan9, can you help me? thank you for the record, you can set the path. e.g. path=($path /some/other/directory) the default path is (. /bin). jaketodd and john correctly point out that this isn't the way it's done; bind(1) is the preferred method. rc (the shell) is the only program that respects $path. in fact that would be a sneeky way to run programs from the shell that can't be exec(2)'d. - erik
Re: [9fans] how can I set path
On Fri, Mar 25, 2011 at 07:57:36AM -0400, erik quanstrom wrote: for the record, you can set the path. e.g. path=($path /some/other/directory) the default path is (. /bin). Probably because one doesn't want to bind . to /bin for every . visited, not because it's a good idea. jaketodd and john correctly point out that this isn't the way it's done; bind(1) is the preferred method. rc (the shell) is the only program that respects $path. in fact that would be a sneeky way to run programs from the shell that can't be exec(2)'d. I read that as allowing the shell to run programs that the kernel would reject. I eventually understood it to mean that you can hide programs where only the shell will find them. Is the current directory one of those places, I wonder? I'm reluctant to figure it out for myself - long day. ++L
Re: [9fans] troff macros for typesetting books/longer texts
On Fri Mar 25 07:52:10 EDT 2011, arn...@skeeve.com wrote: I really like the GNU project's Texinfo markup language, which sets on top of TeX, but you don't have to know TeX. (I've been using Texinfo for 20 years, but don't know any TeX.) I've written books in troff, Docbook/XML, and Texinfo, and Texinfo is by far the easiest. i never could get past the fact that texbook reeks of hubris and nih, nor forgive gnu for using info as an excuse for not having man pages. that, and the fact that it's at least 100x slower than troff, and the reader requires cursor addressing. - erik
Re: [9fans] troff macros for typesetting books/longer texts
On Fri, Mar 25, 2011 at 08:25:27AM -0400, erik quanstrom wrote: i never could get past the fact that texbook reeks of hubris and nih, nor forgive gnu for using info as an excuse for not having man pages. that, and the fact that it's at least 100x slower than troff, and the reader requires cursor addressing. And info is in a league of counter-intuitiveness all of its own. ++L
Re: [9fans] how can I set path
I read that as allowing the shell to run programs that the kernel would
reject. I eventually understood it to mean that you can hide programs
where only the shell will find them. Is the current directory one of
those places, I wonder? I'm reluctant to figure it out for myself -
long day.
try this:
cd $home/tmp
cat diff
#!/bin/rc
echo hi!
EOT
chmod a+x diff
history -D $somefile
diff $somefile `{yesterday $somefile}
- erik
Re: [9fans] how can I set path
On 25 March 2011 12:27, erik quanstrom quans...@quanstro.net wrote:
I read that as allowing the shell to run programs that the kernel would
reject. I eventually understood it to mean that you can hide programs
where only the shell will find them. Is the current directory one of
those places, I wonder? I'm reluctant to figure it out for myself -
long day.
try this:
cd $home/tmp
cat diff
#!/bin/rc
echo hi!
EOT
chmod a+x diff
history -D $somefile
diff $somefile `{yesterday $somefile}
i always set $path to (/bin .)
it can be much faster, apart from anything else.
Re: [9fans] how can I set path
On 25 March 2011 13:53, roger peppe rogpe...@gmail.com wrote:
i always set $path to (/bin .)
it can be much faster, apart from anything else.
% 9fs sources
% cd /n/sources
% echo $path
/bin .
% time rc -c '{for(i in `{seq 1 100}){echo $i}}' /dev/null
0.01u 0.09s 0.27rrc -c {for(i in `{seq 1 100}){echo $i}}
% path=(. /bin)
% time rc -c '{for(i in `{seq 1 100}){echo $i}}' /dev/null
0.00u 0.09s 12.20r rc -c {for(i in `{seq 1 100}){echo $i}}
%
Re: [9fans] troff macros for typesetting books/longer texts
My theory is that GNU tools were so bloated by design that they realized that they couldn't write a decent man page for their tools so they invented the info pages and the --help flag. On Fri, Mar 25, 2011 at 1:25 PM, erik quanstrom quans...@quanstro.net wrote: On Fri Mar 25 07:52:10 EDT 2011, arn...@skeeve.com wrote: I really like the GNU project's Texinfo markup language, which sets on top of TeX, but you don't have to know TeX. (I've been using Texinfo for 20 years, but don't know any TeX.) I've written books in troff, Docbook/XML, and Texinfo, and Texinfo is by far the easiest. i never could get past the fact that texbook reeks of hubris and nih, nor forgive gnu for using info as an excuse for not having man pages. that, and the fact that it's at least 100x slower than troff, and the reader requires cursor addressing. - erik
Re: [9fans] troff macros for typesetting books/longer texts
On Friday 25 of March 2011 16:10:28 pmarin wrote: My theory is that GNU tools were so bloated by design that they realized that they couldn't write a decent man page for their tools so they invented the info pages and the --help flag. coil!dexen!~ $ 9 man rc | wc -l 496 coil!dexen!~ $ man bash | wc -l 5351 coil!dexen!~ $ zcat /usr/info/bash.info.gz | wc -l 10348 coil!dexen!~ $ 9 man mk | wc -l 416 coil!dexen!~ $ zcat /usr/info/make.info* | wc -l 12306 -- dexen deVries [[[↓][→]]] ``In other news, STFU and hack.'' mahmud, in response to Erann Gat's ``How I lost my faith in Lisp'' http://news.ycombinator.com/item?id=2308816
Re: [9fans] troff macros for typesetting books/longer texts
Well, I think it's more that Richard Stallman was so ridiculously in love with ITS's documentation system (which was pretty good for its time, I admit) that he decided to clone it for Unix. Could the bloat of GNU tools merely be a ploy by rms to force people into using info? :) John On Fri, Mar 25, 2011 at 8:10 AM, pmarin pmarin.m...@gmail.com wrote: My theory is that GNU tools were so bloated by design that they realized that they couldn't write a decent man page for their tools so they invented the info pages and the --help flag. On Fri, Mar 25, 2011 at 1:25 PM, erik quanstrom quans...@quanstro.net wrote: On Fri Mar 25 07:52:10 EDT 2011, arn...@skeeve.com wrote: I really like the GNU project's Texinfo markup language, which sets on top of TeX, but you don't have to know TeX. (I've been using Texinfo for 20 years, but don't know any TeX.) I've written books in troff, Docbook/XML, and Texinfo, and Texinfo is by far the easiest. i never could get past the fact that texbook reeks of hubris and nih, nor forgive gnu for using info as an excuse for not having man pages. that, and the fact that it's at least 100x slower than troff, and the reader requires cursor addressing. - erik
Re: [9fans] troff macros for typesetting books/longer texts
Evidence: http://jfloren.net/its-info.png That's a screenshot of Info running on an ITS system :) John On Fri, Mar 25, 2011 at 8:32 AM, John Floren j...@jfloren.net wrote: Well, I think it's more that Richard Stallman was so ridiculously in love with ITS's documentation system (which was pretty good for its time, I admit) that he decided to clone it for Unix. Could the bloat of GNU tools merely be a ploy by rms to force people into using info? :) John On Fri, Mar 25, 2011 at 8:10 AM, pmarin pmarin.m...@gmail.com wrote: My theory is that GNU tools were so bloated by design that they realized that they couldn't write a decent man page for their tools so they invented the info pages and the --help flag. On Fri, Mar 25, 2011 at 1:25 PM, erik quanstrom quans...@quanstro.net wrote: On Fri Mar 25 07:52:10 EDT 2011, arn...@skeeve.com wrote: I really like the GNU project's Texinfo markup language, which sets on top of TeX, but you don't have to know TeX. (I've been using Texinfo for 20 years, but don't know any TeX.) I've written books in troff, Docbook/XML, and Texinfo, and Texinfo is by far the easiest. i never could get past the fact that texbook reeks of hubris and nih, nor forgive gnu for using info as an excuse for not having man pages. that, and the fact that it's at least 100x slower than troff, and the reader requires cursor addressing. - erik
Re: [9fans] how can I set path
On 3月25日, 下午12时22分, 34261...@qq.com (流明) wrote: I'm new to plan9. i don't know how to set path on plan9, can you help me? thank you. 你好，能帮个忙吗？ 我从贝尔实验室下载plan9速度太慢了， 能不能给我传个安装文件 可以QQ或者Email联系 先谢了
Re: [9fans] troff macros for typesetting books/longer texts
On Fri, 25 Mar 2011 08:25:27 EDT erik quanstrom quans...@quanstro.net wrote: On Fri Mar 25 07:52:10 EDT 2011, arn...@skeeve.com wrote: I really like the GNU project's Texinfo markup language, which sets on top of TeX, but you don't have to know TeX. (I've been using Texinfo for 20 years, but don't know any TeX.) I've written books in troff, Docbook/XML, and Texinfo, and Texinfo is by far the easiest. i never could get past the fact that texbook reeks of hubris and nih, nor forgive gnu for using info as an excuse for not having man pages. that, and the fact that it's at least 100x slower than troff, and the reader requires cursor addressing. I am with you on Texinfo, and manpages are vastly preferable over info files but TeX/latex can be used to produce some beautiful text. See The Beauty of Latex page for some examples: http://nitens.org/taraborelli/latex For a much larger example: http://www.duo.uio.no/publ/informatikk/2008/81971/uggedal.pdf
Re: [9fans] troff macro II
Just put the header at the bottom of the page and pipe the .ps output through sed to change the vertical position. Ok. That's a 'dirty' solution, a hack. Though possible. I am looking for a solution within troff, if possible. Thanks anyway Ruda
Re: [9fans] info bashing
My theory is that GNU tools were so bloated by design that they realized that they couldn't write a decent man page for their tools so they invented the info pages and the --help flag. In fairness to info, you have to consider its history. The want was to be able to present an online edition of some large documents (the emacs documentation), with cross-references, search capabilities, index lookups, etc. This was long before the web was even a glimmer in anyone's eye. In that regard, it was a spectacular success. Being able to jump around a 400+page document in real time on a VT100 plugged into a Sun 3/50 workstation is a testament to that. The standalone implementation suffers from being keystroke compatible with the emacs lisp implementation. Those of us who grep up on emacs can find our way around. For anyone else, I can't imagine how they manage to use it. But as others have said, treating info as a replacement for man pages is arrogance beyond any rational description. Then again, the quality of documentation for most GNU software matches that of the code. --lyndon
Re: [9fans] info bashing
In fairness to info, you have to consider its history. The want was to be able to present an online edition of some large documents (the emacs documentation), with cross-references, search capabilities, index lookups, etc. This was long before the web was even a glimmer in anyone's eye. In that regard, it was a spectacular success. Being able to jump around a 400+page document in real time on a VT100 plugged into a Sun 3/50 workstation is a testament to that. i take this as another strike against info. the fact that one sees that the editor's docs are 400+ pages, and there's no easy way to cut that down to a man page, and yet they proceeded to build bloatware to accomidate bloatware. it's like instead of taking a bath, you buy a monster air filter, so no one will notice the stench. - erik
Re: [9fans] info bashing
i take this as another strike against info. the fact that one sees that the editor's docs are 400+ pages, and there's no easy way to cut that down to a man page, and yet they proceeded to build bloatware to accomidate bloatware. That's like blaming Mozilla because you choose to read Sarah Palin's missives with Firefox. --lyndon
Re: [9fans] info bashing
On Fri Mar 25 15:15:59 EDT 2011, lyn...@orthanc.ca wrote: i take this as another strike against info. the fact that one sees that the editor's docs are 400+ pages, and there's no easy way to cut that down to a man page, and yet they proceeded to build bloatware to accomidate bloatware. That's like blaming Mozilla because you choose to read Sarah Palin's missives with Firefox. your defense of info was that it was built to be read a 400+ page reference for emacs. my claim is that if you find a reasonable editor, you won't have a need for info. - erik
Re: [9fans] drawterm bug
On Tue, 22 Mar 2011 13:02 -0500, Jeff Sickel j...@corpus-callosum.com wrote: On Mar 22, 2011, at 12:51 PM, erik quanstrom wrote: back in the right order. Needs work, well, time, it takes time. hey, wait a second ... i thought that was the whole point of hg, to save time. :-) It does, as long as you don't use certain extensions. there were some definate gotchas - hg diff doesn't do the right thing with a patch queue. - hg qpush is terribly misnamed; and hg push --mq is just a poke in the eye. - bitbucket tracks qupdate not qcommit. i don't understand this. Cloning and not using quilted patch queues does man you can work along in your branch of code as needed. Flush out a change, diff it w/ someone other revision/tip/repository and go to town. Export the changes upstream and it is a bit easier, even push them. I've just not taken the time to fully grok the way Bitbucket and a few others use mq. Too much complexity triggers the trap. What on Earth is a quilted patch queue? I always thought the whole point of using a drcs was that you could work in your own branch. I've only used a drcs once, but everyone had their own branch there it went pretty smoothly.
Re: [9fans] drawterm bug
On Friday 25 of March 2011 20:48:50 Ethan Grammatikidis wrote: What on Earth is a quilted patch queue? I always thought the whole point of using a drcs was that you could work in your own branch. I've only used a drcs once, but everyone had their own branch there it went pretty smoothly. I believe branches in hg are somewhat permanent. Your branches have direct, one-to-one, relationship with remote ones. Also, you can't exactly remove a branch in it, AFAIK. But there is `Local Branch Extension' available. after using hg for some time, i went for git where branches are more ephemeral. no idea why this group shuns git, but i'm in no position to proselytise. perhaps porting fossil (the dvcs) [1] to plan 9 would be a good option? [1] an unfortunate name conflict -- aside of the fossil archival filesystem there is fossil DVCS (by the sqlite guys), implemented in C (probably c99 flavor) http://en.wikipedia.org/wiki/Fossil_(software) -- dexen deVries ``One can't proceed from the informal to the formal by formal means.''
[9fans] mark shaney again...
thought this might bring a wry smile to some: Fake Tweets by 'Socialbot' Fool Hundreds of Followers, New Scientist, (03/24/11), Jim Giles Three socialbots recently integrated themselves into a group of Twitter users, gained more than 250 followers, and received more than 240 responses to the tweets they sent over a two-week period as part of Socialbots 2011, a competition designed to test whether bots can be used to change the structure of a social network. The bots were rewarded for the number of followers they obtained and the number of responses their tweets resulted in. The socialbots analyzed tweets sent by members of the network who shared a particular interest and then created a suitable response. The best-peforming bot gained more than 100 followers and generated about 200 responses. Socialbots 2011 organizer Tim Hwang says the bots were able to heavily shape and distort the structure of the network. We could use these bots in the future to encourage social participation or support for humanitarian causes. Hwang has already planned the next socialbot project. We're going to survey and identify two sites of 5,000-person unconnected Twitter communities, and over a six- to 12-month period use waves of bots to thread and rivet those clusters together into a directly connected social bridge between those two formerly independent groups, he says. http://www.newscientist.com/article/mg20928045.100-fake-tweets-by-socialbot-fool-hundreds-of-followers.html -Steve
Re: [9fans] troff macros for typesetting books/longer texts
On Fri, Mar 25, 2011 at 11:32 AM, John Floren j...@jfloren.net wrote: Well, I think it's more that Richard Stallman was so ridiculously in love with ITS's documentation system (which was pretty good for its time, I admit) that he decided to clone it for Unix. Could the bloat of GNU tools merely be a ploy by rms to force people into using info? :) To be fair, Unix tools were getting bloated even without GNU (cat -v, anyone?). GNU just introduced the --verbose-lispmachine-style-option-syntax to the mess. Frankly, I think that's the problem with a lot of GNU stuff: it was made by RMS and other folks who mainly came out of the PDP-10 and LISP Machine tradition which doesn't really mesh well with the Unix tradition. Programs with lots of options were IMPORTANT when your shell environment was really just a hacked up version of a debugger from the mid-60s because you didn't have things like pipes to make programs play nice together. On the other end, having a verbose syntax didn't really matter when you were working with a smart LISP system or TWENEX or some other system with really good completion support. Thus the problems with GNU can be directly traced to the fact that it was written by people with brains scrambled by DDT on the one hand and spoiled by TWENEX and standalone LISP on the other. Mike
Re: [9fans] mark shaney again...
On Fri, 2011-03-25 at 20:16 +, Steve Simon wrote: Fake Tweets by 'Socialbot' Fool Hundreds of Followers, New Scientist, (03/24/11), Jim Giles http://captology.stanford.edu/
Re: [9fans] mark shaney again...
On Fri, Mar 25, 2011 at 08:16:59PM +, Steve Simon wrote: Fake Tweets by 'Socialbot' Fool Hundreds of Followers, New Scientist, (03/24/11), Jim Giles This is not new. Politicians are socialbots generating sentences from a limited set of politically correct chunks (this means: that don't make sense) and have, still, millions of followers... and cause millions of deaths too... And a majority of research papers could be made by socialbots too (the difference with today is that every fake researcher is doing the swindle by hand---I mean by mouse). -- Thierry Laronde tlaronde +AT+ polynum +dot+ com http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: [9fans] mark shaney again...
This is not new. Politicians are socialbots generating sentences from a limited set of politically correct chunks (this means: that don't make sense) and have, still, millions of followers... and cause millions of deaths too... Listen, just because we called an election today ... wait! Where's my research grant?!?
Re: [9fans] troff macro II
Read carefully the section 9, 10 and 11 of A TROFF Tutorial[1]. I
think is exactly what you are looking for.
[1] http://www.kohala.com/start/troff/v7man/trofftut/trofftut.ps
On Thu, Mar 24, 2011 at 5:54 PM, Rudolf Sykora rudolf.syk...@gmail.com wrote:
Hello 9fans,
since in the previous thread started by me ('troff macros for
typesetting books/longer texts') nobody touched my question about
producing wanted headings, I started experimenting, but so far has not
been quite successful.
Since text to appear in my headings is to mirror section names, like
'1.2', and a beginning of such a section appears somewhere lower on a
page---definitely below the page heading---, I must create a page
heading just after the very page is filled, i.e., as I feel, the
heading could actually be produced when the ms .BT macro (usually used
to typeset footings) is called. So I naively tried to redefine the .BT
macro, actually, by just appending 4 extra lines:
.de BT
.nr PX \\n(.s
.nr PF \\n(.f
.ft 1
.ps \\n(PS
'lt \\n(LTu
.po \\n(POu
.if \\n%0 .tl \(ts\\*(LF\(ts\\*(CF\(ts\\*(RF\(ts
.ft \\n(PF
.ps \\n(PX
.\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX
.mk
\v'|0.5i'
.tl 'a'b'c'
.rt
..
Please consider this just as an experiment (no point-size changes,...).
This for some reason doesn't work.
Since some of you probably have experience, could sb. tell what is wrong?
Thank you
Ruda
Re: [9fans] drawterm bug
On Mar 25, 2011, at 3:09 PM, dexen deVries wrote: On Friday 25 of March 2011 20:48:50 Ethan Grammatikidis wrote: What on Earth is a quilted patch queue? I always thought the whole point of using a drcs was that you could work in your own branch. I've only used a drcs once, but everyone had their own branch there it went pretty smoothly. It's a made up reference to the mq extension (search for 'quilt'): http://mercurial.selenic.com/wiki/MqExtension I believe branches in hg are somewhat permanent. Your branches have direct, one-to-one, relationship with remote ones. Also, you can't exactly remove a branch in it, AFAIK. But there is `Local Branch Extension' available. Hg branching is very different than the use of the queues extension. I've had decent success using hg branches in the past, much safer and easier to manage than queues. after using hg for some time, i went for git where branches are more ephemeral. no idea why this group shuns git, but i'm in no position to proselytise. perhaps porting fossil (the dvcs) [1] to plan 9 would be a good option? Personally I went the hg route instead of git for a few reasons: - it was easier to build Python and install Hg on the targets I needed than to build/install most of the other options at the time. - at the time getting git to run on anything but a few distros of gnu/linux was more effort for less bang, if not ending up in a fizzle. It's easier now that the coding monkeys have taken on the task of releasing git into the wild. - the alignment with tools I'd used in the past fit well. Hg branching and merging work a lot like devman (another tool killed by sun(tm), and some other tools I've used. It's not the only dvcs out there, but it's got good backing and runs everywhere python is available (which is more than the current git targets). Though I'd like to rely on venti, it's not really a source control system. Metadata about a change can be important if managed well, especially in large groups. There has been discussion on this list about trying to come up with a more Plan 9-influenced source revision system. -jas
[9fans] dst shift is shifty
Am I the only person still an hour behind the PST-PDT shift? I recall this happening last year, too ...
Re: [9fans] troff macro II
DONE!
Try the attached code. I am not using the ms macros. You will to
change the ms macros to get something similar.
troff test.ms | tr2post | psfonts test.ps
Cheers.
pmarin
On Thu, Mar 24, 2011 at 5:54 PM, Rudolf Sykora rudolf.syk...@gmail.com wrote:
Hello 9fans,
since in the previous thread started by me ('troff macros for
typesetting books/longer texts') nobody touched my question about
producing wanted headings, I started experimenting, but so far has not
been quite successful.
Since text to appear in my headings is to mirror section names, like
'1.2', and a beginning of such a section appears somewhere lower on a
page---definitely below the page heading---, I must create a page
heading just after the very page is filled, i.e., as I feel, the
heading could actually be produced when the ms .BT macro (usually used
to typeset footings) is called. So I naively tried to redefine the .BT
macro, actually, by just appending 4 extra lines:
.de BT
.nr PX \\n(.s
.nr PF \\n(.f
.ft 1
.ps \\n(PS
'lt \\n(LTu
.po \\n(POu
.if \\n%0 .tl \(ts\\*(LF\(ts\\*(CF\(ts\\*(RF\(ts
.ft \\n(PF
.ps \\n(PX
.\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX
.mk
\v'|0.5i'
.tl 'a'b'c'
.rt
..
Please consider this just as an experiment (no point-size changes,...).
This for some reason doesn't work.
Since some of you probably have experience, could sb. tell what is wrong?
Thank you
Ruda
test.ms
Description: Troff MS-macros document
Re: [9fans] dst shift is shifty
On Fri Mar 25 17:48:43 EDT 2011, lyn...@orthanc.ca wrote: Am I the only person still an hour behind the PST-PDT shift? I recall this happening last year, too ... i thought i fixed the timezone files a couple of years ago. ladd; date Fri Mar 25 18:07:09 EDT 2011 ladd; timein US_Pacific Fri Mar 25 15:07:23 PDT 2011 did you not copy the new US_Pacific to /adm/timezone/local? - erik
Re: [9fans] dst shift is shifty
did you not copy the new US_Pacific to /adm/timezone/local? Being in Canada_Pacific, no. I see an update is required.
Re: [9fans] troff macro II
On 25 March 2011 22:52, pmarin pmarin.m...@gmail.com wrote: DONE! Try the attached code. I am not using the ms macros. You will to change the ms macros to get something similar. troff test.ms | tr2post | psfonts test.ps Cheers. pmarin Yes. This works. Actually, my problem has always only been: how to get back to the top of a page; to have a correct string prepared to put there has been easy for me. Note what I wrote in my 1st post of this thread: . .\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX .mk \v'|0.5i' .tl 'a'b'c' .rt .. and it comes in a modified .BT macro (which is somewhat equivalent to your .NP; ms actually sets [as far as I know] 3 traps on a page, 1 at the top [.NP] and 2 at the bottom [.FO a .BT]). If I had written just . .\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX .tl '\v'-10.5i'a'b'c\v'+10.5i'' .. as you have, it would have basically done what I want. So now the question is why .tl '\v'-10.5i'a'b'c\v'+10.5i'' moves back and does the work, whilst .mk \v'|0.5i' .tl 'a'b'c' .rt does not. Nor does this, for instance: \v'-10.5i' .tl 'a'b'c' \v'+10.5i' Thanks for your help Ruda
Re: [9fans] troff macro II
Becouse The backslash character \ is used to introduce troff commands and special characters *within* a line of text (from the Troff tutorial) Try: .\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX .mk .tl '\v'-10.5i'a'b'c\v'+10.5i'' .rt .. On Sat, Mar 26, 2011 at 1:10 AM, Rudolf Sykora rudolf.syk...@gmail.com wrote: On 25 March 2011 22:52, pmarin pmarin.m...@gmail.com wrote: DONE! Try the attached code. I am not using the ms macros. You will to change the ms macros to get something similar. troff test.ms | tr2post | psfonts test.ps Cheers. pmarin Yes. This works. Actually, my problem has always only been: how to get back to the top of a page; to have a correct string prepared to put there has been easy for me. Note what I wrote in my 1st post of this thread: . .\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX .mk \v'|0.5i' .tl 'a'b'c' .rt .. and it comes in a modified .BT macro (which is somewhat equivalent to your .NP; ms actually sets [as far as I know] 3 traps on a page, 1 at the top [.NP] and 2 at the bottom [.FO a .BT]). If I had written just . .\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX .tl '\v'-10.5i'a'b'c\v'+10.5i'' .. as you have, it would have basically done what I want. So now the question is why .tl '\v'-10.5i'a'b'c\v'+10.5i'' moves back and does the work, whilst .mk \v'|0.5i' .tl 'a'b'c' .rt does not. Nor does this, for instance: \v'-10.5i' .tl 'a'b'c' \v'+10.5i' Thanks for your help Ruda
Re: [9fans] troff macro II
Also to pay attention to the command .wh in my example: .wh -1i NP \ When you reach the final of the page less 1 inch call the command .NP On Sat, Mar 26, 2011 at 2:02 AM, pmarin pmarin.m...@gmail.com wrote: Becouse The backslash character \ is used to introduce troff commands and special characters *within* a line of text (from the Troff tutorial) Try: .\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX .mk .tl '\v'-10.5i'a'b'c\v'+10.5i'' .rt .. On Sat, Mar 26, 2011 at 1:10 AM, Rudolf Sykora rudolf.syk...@gmail.com wrote: On 25 March 2011 22:52, pmarin pmarin.m...@gmail.com wrote: DONE! Try the attached code. I am not using the ms macros. You will to change the ms macros to get something similar. troff test.ms | tr2post | psfonts test.ps Cheers. pmarin Yes. This works. Actually, my problem has always only been: how to get back to the top of a page; to have a correct string prepared to put there has been easy for me. Note what I wrote in my 1st post of this thread: . .\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX .mk \v'|0.5i' .tl 'a'b'c' .rt .. and it comes in a modified .BT macro (which is somewhat equivalent to your .NP; ms actually sets [as far as I know] 3 traps on a page, 1 at the top [.NP] and 2 at the bottom [.FO a .BT]). If I had written just . .\ ABOVE IS THE ORIGINAL, BELOW MY APPENDIX .tl '\v'-10.5i'a'b'c\v'+10.5i'' .. as you have, it would have basically done what I want. So now the question is why .tl '\v'-10.5i'a'b'c\v'+10.5i'' moves back and does the work, whilst .mk \v'|0.5i' .tl 'a'b'c' .rt does not. Nor does this, for instance: \v'-10.5i' .tl 'a'b'c' \v'+10.5i' Thanks for your help Ruda
Re: [9fans] dst shift is shifty
On Fri Mar 25 18:54:59 EDT 2011, lyn...@orthanc.ca wrote: did you not copy the new US_Pacific to /adm/timezone/local? Being in Canada_Pacific, no. I see an update is required. hmmm. iirc, i made the us change when the law in canada was in doubt. sorry for falling down on the job. as a hack, if you copy US_Pacific, except for the dates from 1973-1974, that should be the right temporary fix ; diff -c /n/sourcesdump/2006/0401/plan9/adm/timezone/US_Pacific US_Pacific /n/sourcesdump/2006/0401/plan9/adm/timezone/US_Pacific:1,6 - Canada_Pacific:1,6 PST -28800 PDT -25200 9943200 25664400 41392800 57718800 73447200 89168400 - 104896800 120618000 126669600 152067600 162352800 183517200 + 104896800 120618000 136346400 152067600 167796000 183517200 i'll submit a patch. - erik
