I don't really want to get into a major revision control system fight
here; as I said earlier it seems to be clearly Werner's decision. I
didn't want to leave undefended assertions lying around though!
I did not use bzr, but based on information I've seen, these are not
"undefended assertions"
On Sep 30, 2008, at 6:14 AM, Ralph Corderoy wrote:
Is there somewhere to raise bugs with Apple so it might get addressed
sometime?
http://developer.apple.com/bugreporter/
Apparently, one needs to register as an Apple Developer.
There is a free registration option.
I intend to do that for a lo
On Sep 29, 2008, at 3:23 PM, Clarke Echols wrote:
On my old setup, I was using groff running in a bash shell as part
of the cygwin package, and got the shareware PostScript viewer
"GSView" which I really like for several reasons.
If you are not after flashy viewers, "gv" is still the best PostS
On Sep 29, 2008, at 3:09 PM, Stefan Tramm wrote:
On Mac OS X 10.5.5 (with all latest patches applied)
eqn(1) seems to be broken!
Confirmed.
Mac OS X Leopard with all the updates applied (same uname -a output as
Stefan's except the host name).
It does not work.
I tried it with the Heirloom
On Wed, Sep 12, 2007 at 10:12:46AM -0400, Webb Roberts wrote:
> What is the easiest way to get a Venn diagram in Groff? Pic doesn't
> seem to like overlapping shapes.
You can get away with hatching.
I attached the file that does a simple variant of that.
Best regards,
Zvezdan
.PS
.fam H
refer after small
modifications.
Best regards,
Zvezdan
.\" ACM-ms.tmac - refer support for -ms
.\"
.\" Conforms to the _Communications of the ACM_ reference style.
.\" The only exception is that author names are not reversed and shortened.
.\"
.\" Zvezdan
On Tue, Mar 13, 2007 at 03:04:21PM -0700, Nick Stoughton wrote:
> Try using tr ... The character '^@' is a null byte (for tr, this is
> '\000'). You can strip out all control chars by:
He asked about ~@, not [EMAIL PROTECTED]
The easiest way to find what it represents is saving it in another file
On Tue, Mar 13, 2007 at 03:15:08PM -0600, Clarke Echols wrote:
> Words are separated by a single character that displays in vim as
> a (blue) couple of characters: ( ~@ ) and there are other characters
> showing up as ( ^U, ^^, ^@, ) etc.I know how to do regular
> expression search and replace
On Mon, Feb 05, 2007 at 12:26:28PM -0500, Eric S. Raymond wrote:
> While we're on the subject, though, I must say that I think traditional
> GNU-style Changelogs are obsolete and irritating. It's a convention that
> made a lot of sense before use of VCSes became common, but nowadays my
> Changelo
On Sat, Feb 03, 2007 at 12:13:40AM +0100, Werner LEMBERG wrote:
> > > Doesn't it look typographically even better as `\|.\|.\|.\&'.
> > > I think this is what eqn sequence `. . .' gets translated into.
> >
> > In general, this depends on language and style guide.
>
> Indeed. Within groff, James
On Sat, Feb 03, 2007 at 12:01:45AM +0100, Gunnar Ritter wrote:
> Zvezdan Petkovic <[EMAIL PROTECTED]> wrote:
>
> > On Fri, Feb 02, 2007 at 07:44:10PM +0100, Werner LEMBERG wrote:
> > > . The proper way to write an ellipsis is `.\|.\|.\&', optionally
> &g
On Fri, Feb 02, 2007 at 07:44:10PM +0100, Werner LEMBERG wrote:
> . The proper way to write an ellipsis is `.\|.\|.\&', optionally
> starting with `\&'. Please don't omit the `\|' -- it looks quite
> ugly in PostScript output if the dots don't have enough horizontal
> separation.
Do
On Wednesday 10 January 2007 18:59, Eric S. Raymond wrote:
> Gunnar Ritter <[EMAIL PROTECTED]>:
> > > I believe you are incorrect. If these definitions are *in the
> > > file*, won't the Solarix/AIX/HP-UX toolchain evaluate them the
> > > same way they would evaluate any other local macro?
> >
> >
I personally use groff for PDF and PostScript documents, so I did not
care for grohtml too much. The recent discussion about doclifter
prompted me to recheck, and it seems to be a little -ms centric.
This is a part of a paragraph from an -me document.
.lp
Let's look again at an $
On Thu, Dec 28, 2006 at 08:51:37PM -0800, Meg McRoberts wrote:
> I'm not sure of the solution but it seems that, if they could write in
> docbook, this opens the option of using an XML WYSIWYG editor if
> necessary.
Which does not make the writing any faster.
Picking one of 100+ tags from the menu
On Thu, Dec 28, 2006 at 11:11:34PM -0500, Eric S. Raymond wrote:
> > There is a deeper philosophical question here.
> > Who needs to tag a document for all the sorts of semantic or any other
> > meaning? Is it the author or somebody else?
>
> Who tags the man pages you write? Who should tag them
On Wed, Dec 27, 2006 at 06:52:13AM -0500, Eric S. Raymond wrote:
> I don't think your citation of -mdoc is really on point. IMO, the
> reason it hasn't gained acceptance is that, while -mdoc markup is
> cleverly designed, it is also quite complex -- more heavyweight than
> most man-page writers wa
On Sat, Dec 23, 2006 at 06:01:29PM -0500, Eric S. Raymond wrote:
> I use Emacs to edit DocBook markup directly.
That's not different from what I've been doing.
I wouldn't say that is a comfortable way of writing.
> For someone as bothered by tag verbosity as you are I would recommend
> using asci
The point here is on "my" in the sentence above.
What Mr. Ritter is saying all this time is that the number of cases
simply does not warrant the _unportable_ change to a well established
legacy format.
If doclifter handles all these cases as well as you already described
there is no need for an ex
On Sat, Dec 23, 2006 at 12:25:01AM -0500, Eric S. Raymond wrote:
> I *am* "skilled hands" in that sense, having done successful
> full-length technical books in all three markups. Speaking from
> that experience, I rate groff better than TeX but inferior to a good
> DocBook toolchain (with the exc
images. This too is now fixed in CVS.
First of all sorry for not responding earlier.
I was on a vacation and couldn't test the new version of pdfroff script.
I checked it out today with and without --no-kill-null-pages option.
It produces the same PostScript file which is good. The pi
agraph of annnotation.
> .LP
> Second paragraph of annotation.
> ..
I believe it would be better if it just turns it into
.LP
First paragraph.
.LP
Second paragraph.
> Anyone know of any way to circumvent this problem?
I hope the above hint helps.
Best regards,
Zvezdan Petkovic
to pdfroff, so that users can make
> the choice, IMHO. (This is something which was discussed before, but I
> simply haven't found the time to implement it).
No need. I call it from Makefile as
env GS_OPTIONS="-dSAFER" pdfroff ...
Ghostscript respects GS_OPTION
I also have defined
PDFROFFOPTS ?= --no-toc-relocation --leave-postscript-only
So I always simply use
${PDFROFF} ${PDFROFFOPTS} ...
The patch against 1.19.2 that creates pdfroff2 is attached below.
Keith is this acceptable to you?
Can it become a part of a regular pdfroff?
Best regar
for you too if you translate SS into your
MDUTBIMI font.
Best regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
lications by defining $HOME/.fonts.conf file
with an entry:
...
LetterGothic
monospace
...
Now I can start
xterm -fa LetterGothic
if I feel so inclined.
I don't.
hic
if I feel so inclined.
I don't.
:-)
I hope this helps.
All the best.
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
#x27;s no need for it.
The expressions \{...\} and \(...\) is a part of BREs (Basic Regular
Expressions) for a long time.
Just my two cents.
Best regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
for BSD.
It's a part of a whole OS, that is maintained as a single CVS tree.
I suggest not to report it though.
I'm quite certain you'd get a reply that it won't be changed from what
POSIX suggests.
Changing the expressions as I suggested above is the easiest path to
take.
I hope this was helpful.
Best regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
X.
> > >
> regards
> amber
Amber, please read it again.
> > Zvezdan Petkovic wrote:
> > > When I get some time, I'll take a careful look at pdfroff script
> > > and see how I can incorporate it in my set of Makefiles.
> > > They work with -mm (be
On Sun, Oct 23, 2005 at 03:05:34AM +0200, Bernd Warken wrote:
>
> Zvezdan Petkovic wrote:
> >
> > There's a good info viewer that is more like lynx than info.
> > It's called pinfo, and I use it all the time for reading info pages.
>
> Another possibili
im window with a list of all DocBook elements.
It doesn't sing or dance though because I stopped working on it the
minute I lost interest in editing more DocBook documents.
:-)
Best regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
ngs are familiar to UNIX users (think 'more') and extra
features of info are supported with bindings that vi(m) users will love.
:-)
If you don't like the default colours you can use my .pinforc attached
below (change mutt to your own mail program; pine was the default).
the markup after writing, because the number of interruptions of
the thought process is mind-boggling otherwise.
Best regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
On Fri, Oct 21, 2005 at 10:23:25AM +0300, Greg 'groggy' Lehey wrote:
> On Thursday, 20 October 2005 at 15:07:32 -0400, Zvezdan Petkovic wrote:
> > Take a look at O'Reilly books (colophon section). Until recently
> > they all were converted from format X into gr
I think that limiting groff to "documentation, memos, letters, and
manuals" is not right.
Regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
asy and short.
Nothing was changed, because this feature was made default in 1.18.
Best regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
ll be respected.
> The important thing is to make sure your build works properly
> before installing it over the default version.
Exactly. Very important point.
Best regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://
n adze.
And again, the guy wanted to use groff on UNIX, so your comparison is
off the base.
> I hope that you agree with this little perspective and then we can go
> back to the wonders and problems of groff.
> With a bit of humility, if possible.
I agree.
We're way off the
ld Joe to go back home and study the basics (in not
very minced words).
Now the teacher is rude, and Joe is the poor victim.
Right.
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
ing
> end of your own post.
I would feel scolded as I do now.
You do not realize that your words are not at all different than mine.
The difference is that I scolded a person who wasted everybody's time
because of his own error.
You are scolding a person who tried to help him extremely
on the first update
of that system part.
I always thought OpenBSD users know better than this.
I wish you good luck and less use of rootly powers for no reason.
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
;
> Hmm, strange. This *must* work since it directly affects grotty. Are
> you sure that your man program doesn't use a hard-coded groff version?
> Is it really using 1.19.2?
It does work. I use OpenBSD 3.7 every day for all my work.
He has messed up something on his system.
together,
but one or the other) when used in my .profile work flawlessly.
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
On Sat, Oct 08, 2005 at 07:22:41PM -0600, D. E. Evans wrote:
> I have installed 1.19.2 (via todays cvs checkout) onto an OpenBSD
> 3.7 system, (which uses 1.15 by default). This also required an
> upgrade of texinfo to 4.8, (both of which I installed from source).
>
> I get the following result w
On Wed, Jul 06, 2005 at 03:36:07PM +0200, Andries Brouwer wrote:
> I am not really aware of use of groff other than as a backend to man.
Now, you are a little upset with Bruno's response, so you are sending a
little jab. Nice. Some people never heard of TeX either and they think
Word (or OpenOff
gns.
Also, vim syntax is allowed to be in the first N lines of the file,
or the last N lines of the file. The default is N=5.
Thus if you need something to be on the first line you can always move
modeline to the end.
Regards,
Zvezdan Petkovic
_
if you use (t)csh.
It works for me on OpenBSD where "more" is a hard link to "less".
$ ls -i /usr/bin/{more,less}
247424 /usr/bin/less 247424 /usr/bin/more
You may need to replace "more" with "less" above.
Regards,
Z
t `.gcolor' and `.fcolor' instead of
> \m and \M, respectively.
And that does it!
My gpresent woes are gone!
I applied the patch from groff-current to groff-1.19.2.pre-20050527
and all my animated pictures in all the presentations work as expected.
Thanks a
.gcolor)
Gpresent now works great!
Thanks again!
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
On Fri, Jun 24, 2005 at 06:00:02PM +0200, Werner LEMBERG wrote:
>
> > Please find attached example for the spacing bug introduced in
> > 1.19.2pre Notice the lack of spacing between picture and the labels
> > below it.
>
> Your macro definition of .Se relies on pic internals which are neither
> d
On Fri, Jun 24, 2005 at 05:53:54PM +0200, Werner LEMBERG wrote:
> Not at all. You don't use the `color' or `shaded' command in PIC, so
> it is completely unrelated.
First of all sorry for not replying earlier.
I was at the conference, and didn't want to hurry through this from a
hotel room withou
Notice that when you switch off the register AK (answer key)
.nr AK 0
then the document looks OK.
So, this must be related to PIC colour handling again.
Sigh.
ZP
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listin
OK with 1.18.x and gives no warnings.
Please advise.
Zvezdan Petkovic
example.me
Description: Troff ME-macros document
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
On Sat, Jun 18, 2005 at 10:29:44PM -0400, Zvezdan Petkovic wrote:
> Werner, you know the best why the change was made in the first place.
> Do you find this fix correct? Is it safe to assume it won't spoil other
> things?
Hmm. Since reset_colors() is called from finish_picture()
sp -1\n");
as in 1.18.1.1. That has fixed the problem with the vertical movement
between the colour changes and pauses, but the picture was bad because
some elements were moved vertically back.
Then I tried the change given in the attached patch and the pics are now
all right. I tried i
the list. I'll send you off the list a tar.gz file with the complete
extracted example (just run make in the directory) and the pdf files of
how it looks like with 1.18.x and how 1.19.x changes it.
The private mail follows.
Best regards,
--
Zvezdan Petkovic <[EMAIL PROTECTED]>
http
On Fri, Jun 17, 2005 at 09:17:49AM +0200, Werner LEMBERG wrote:
> Unfortunately, I've never used gpresent, so I can't help here due to
> lack of time. Please contact the author of this package for
> assistance in debugging.
I did a couple of months ago.
He concluded that it's a groff bug.
And it
I had to apply the attached patch to build groff-1.19.2.pre-20050527 on
OpenBSD 3.7. Keith uses $(RM) without ever defining it. I checked
through the whole groff source tree and it's not defined anywhere.
Thus those lines were failing trying essentially to execute the argument
to $(RM). This sol
Pic bug that started in 1.19.x series is still not fixed.
Gpresent .PAUSE request, in combination with pic for loop, triggers a
vertical move which screws up a picture.
See the attached file for the example pic code.
Make a picture. Then
add
.copy "animate.pic"
after .PS
and instead of ev
provided appropriate portability guidlines are followed.
Couldn't agree more!
Best regards,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
No surprise considering what you get after running
strings /usr/bin/* | grep BSD
on Windows SFU.
:-)
Therefore, any script should start with #!/bin/sh because that is the
only portable way.
Best regards,
Zvezdan Petkovic
___
Groff maili
I think that previous Rago's book
Stephen A. Rago. 1993.
UNIX System V Network Programming.
Reading, MA: Addison-Wesley
ISBN: 0201563185
has been published in groff too.
However, people who own Rago's book should check.
Will you please?
Zvezdan Petkovic
ntroduce changes without thinking them through.
Sorry for the noise.
All the best,
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
w to make tryme. Stop in /home/zvezdan.
$ gmake tryme
g++ tryme.cpp -o tryme
Obviously only gmake recognizes .cpp as a C++ file on a Unix system.
With older version of gmake on a different Unix machine .cpp has not
been recognized.
Regards,
Zvezdan Petkovic
___
On Fri, May 06, 2005 at 03:51:17AM +0100, Keith Marshall wrote:
> On Thursday 05 May 2005 7:40 pm, Zvezdan Petkovic wrote:
> > BTW, I don't think Cygwin should be a measure of Unix compatibility.
>
> Possibly not; but, like it or not, Microsoft Windows has the largest user
On Thu, May 05, 2005 at 10:42:13AM +0100, Keith MARSHALL wrote:
> Larry Jones wrote, quoting Zvezdan Petkovic:
> >> So the solution is to use command -v.
> >
> > Hardly -- "type" is probably more portable than "command -v" is.
> > Particularly si
complish here, the
POSIX command utility was enhanced and the historical utilities
were left unmodified. The C shell which merely conducts a path
search. The KornShell whence is more elaborate-in addition to
the categories required by POSIX, it also reports on tracked
aliases, exported aliases, and undefined functions.
So the solution is to use command -v.
All the best.
Zvezdan Petkovic
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
8.1.1?
FWIW, the only reason I do not use 1.19 branch is that it doesn't work
with gpresent. The request .PAUSE inside a pic creates a vertical move,
and the figure ends up quite different from what it should be. :-)
Has anything been done to address this issue?
Zvezdan Petkovic
t in a document, it can be done as
.R1
join-authors ", and " ", " ", and "
.R2
The default is, as you show above
.R1
join-authors " and " ", " ", and "
.R2
I believe you can insert this in mom's implementation of
refer support.
Rega
70 matches
Mail list logo
