Branches
Comments
[»]
Downtime and relocation notice 2008 June 24
by Wolfpack Entertainment - Jun 25th 2008 03:09:39
The site (revealsystems.net) that hosts this project's web page
(battlefieldlinux.com) was destroyed by error in behalf of a repair
technitian attempting to fix another site physically adjacent to this site
on 2008 June 12. This site was incorrectly identified as the site needing
repair by the technitian and all of its data was completely erased by the
"repair" which involved an attempt to install a different
operating system (Windows 2000).
Corrective actions are pending on the technitian as of this posting.
We are currently regenerating our source and data packages and using
wolfsinger.com and savannah.gnu.org as a temporary distribution point. We
have not made a decision at this point as to whether to keep this temporary
distribution set up or to recreate the set up on battlefieldlinux.com. When
a decision is made it will be posted here.
[reply]
[top]
[»]
special characters
by Dev0 - Nov 28th 2001 16:11:27
It would have been nice if I told why :) ...
If you start a line with a dot it doesn't show although the line is
present in the manual file. It looks like it is interpreted as a hidden
file (e.g. .bashrc) or something... any clues?
[reply]
[top]
[»]
Re: special characters
by Dev0 - Nov 28th 2001 18:04:53
> It would have been nice if I told why :)
> ...
> If you start a line with a dot it
> doesn't show although the line is
> present in the manual file. It looks
> like it is interpreted as a hidden file
> (e.g. .bashrc) or something... any
> clues?
Okay, after the usual RTFM stuff apparently a possible way for this is
starting the line using \N'046' .
In my current font this will produce the dot I need.
Still open for suggestion tho :)
[reply]
[top]
[»]
Re: special characters
by Dev0 - Nov 29th 2001 03:11:11
> It would have been nice if I told why :)
> ...
> If you start a line with a dot it
> doesn't show although the line is
> present in the manual file. It looks
> like it is interpreted as a hidden file
> (e.g. .bashrc) or something... any
> clues?
Wow, I found in a side-related manual another one.
One can also start a line with "\&."
[reply]
[top]
[»]
special characters
by Dev0 - Nov 28th 2001 15:59:06
How does one start a line with a dot in manedit like:
. <program name>
A \ as 'do nothing with next character' doesn't work and the manual
doesn't tell.
[reply]
[top]
[»]
Wysiwyg?
by Arthur H. Johnson II - Aug 9th 2001 11:18:09
It would be nice if it was what-you-see-is-what-you-get.
[reply]
[top]
[»]
Re: Wysiwyg?
by Wolfpack Entertainment - Aug 10th 2001 19:18:08
> It would be nice if it was
> what-you-see-is-what-you-get.
Hit the Preview button get see a preview
of the finished page.
The editing of manual pages is much like the
editing of web pages, they're based on
what you mean
rather than what you see. It's very
CPU intensive to generate a what you see
output, since every modification needs to be passed through your system's
manual groff interpriter
(and that is after converting from
XML to groff format).
[reply]
[top]
|
