Re: [Groff] Automake migration proposal

2014-09-03 Thread Werner LEMBERG
> |> There should be a note that on Snow Leopard you have to set $CXX to > |> an upgrade compiler -- the developer-toold shipped `Apple clang > |> version 1.7 (tags/Apple/clang-77) (based on LLVM 2.9svn)' bails: > |> [...] > | > |Can you please provide a patch for groff's `PROBLEMS' file?

Re: [Groff] [groff] 01/01: contrib/mom: license and Emacs setup; ChangeLog: repair it.

2014-09-03 Thread Werner LEMBERG
> contrib/mom: license and Emacs setup; ChangeLog: repair it. Bernd, I generally applause your efforts on normalizing those issues. However, `mom' is actively maintained by Peter, and your changes are quite substantial, so please contact him in advance whether he likes your modifications.

[Groff] A licensing question for forking GNU troff

2014-09-03 Thread Steffen Nurpmeso
Hello, i am in the process of forking an old version of GNU troff, starting from the last commit that is still GPL2 licensed (1.19.2-574-gecbf4f1). It is yet nothing but a bubble full of air, of course. (It will be S-roff.) I planned to place all completely new code (like file_case) under the I

Re: [Groff] Extending refer

2014-09-03 Thread Steffen Nurpmeso
Pierre-Jean wrote: |Werner LEMBERG wrote: |> I've just seen this: |> |> http://ftp.fi.muni.cz/pub/bibliography/tools/bibtex2refer | |This is, for sure, a handy script. I also thought so and ran it on [1] (the first link i got) and schwuppdiwupp i ended in an endless loop. Find attached a

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Carsten Kunze
> .do xflag 3 > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B > .char " "\| > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B > > Output "A is like A" and "B is like B" only once. It is fixed on GitHub now. Thanx for the bug report.

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Tadziu Hoffmann
> Output "A is like A" and "B is like B" only once. You mean, only once on the terminal? Do you get any text in the output file?

Re: [Groff] Extending refer

2014-09-03 Thread Pierre-Jean
Werner LEMBERG wrote: > I've just seen this: > > http://ftp.fi.muni.cz/pub/bibliography/tools/bibtex2refer This is, for sure, a handy script. Zotero (a firefox and OpenOffice plugin, which extract bibliography references from web pages, store them, and insert them in office texts) can also dea

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Carsten Kunze
> .do xflag 3 > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B > .char " "\| > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B Sorry, I didn't notice the |. You're right, there is a problem.

Re: [Groff] Extending refer

2014-09-03 Thread Werner LEMBERG
> That said, it would be nice to share a refer database of the > various troff (and maybe unix) papers, which are sometimes > mentionned on man pages. I've just seen this: http://ftp.fi.muni.cz/pub/bibliography/tools/bibtex2refer I can imagine that such a tool could be improved so that the ma

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Carsten Kunze
> .char " "\| Maybe it wold be better to say .ec # .char " "\#& .ec

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Carsten Kunze
> I've found another bug in Heirloom troff (with ^G being the > control character, "Ctrl+V + Ctrl+G" in vim): > > .do xflag 3 > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B > .char " "\| > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B > > Output "A is like A" and "B is lik

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Carsten Kunze
> .do xflag 3 > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B > .char " "\| > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B I have not tested it yet. But please add a \& to the .char line. \ as the last char on a line has a special meaning.

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Tadziu Hoffmann
> But does anyone know what does this character means, and why > does it seems to be prefered to other control characters ? It's the "bell" character. On output, it rings the terminal bell, but doesn't have any other side effects. Try this in bash: echo -e '\007' (octal 007 is ASCII BEL).

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Keith Marshall
On 03/09/14 20:12, Carsten Kunze wrote: >> I've recently seen the usage of the ^G character as field >> separator. That is a good idea, since it should avoid most >> possible conflicts with user input. But does anyone know >> what does this character means, and why does it seems to be >> prefered t

Re: [Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Carsten Kunze
> I've found another bug in Heirloom troff (with ^G being the > control character, "Ctrl+V + Ctrl+G" in vim): > > .do xflag 3 > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B > .char " "\| > .if "A"A" .tm A is like A > .if ^GB^GB^GB .tm B is like B > > Output "A is like A" and "B is l

[Groff] [Heirloom] bug in '.if' string comparison tests

2014-09-03 Thread Pierre-Jean
Hello Alls, I've found another bug in Heirloom troff (with ^G being the control character, "Ctrl+V + Ctrl+G" in vim): .do xflag 3 .if "A"A" .tm A is like A .if ^GB^GB^GB .tm B is like B .char " "\| .if "A"A" .tm A is like A .if ^GB^GB^GB .tm B is like B Output "A is like A" and "B is like B" on

Re: [Groff] Extending refer

2014-09-03 Thread Pierre-Jean
"Bernd Warken" wrote: > 1) `refer.man' cites under `FILES': > file.i Index files. I did not investigate this much, but this should be the conventional output file name of the 'mkey' program from Heirloom/refer, which build an index of keys of a refer file. Another program, 'inv

Re: [Groff] [groff] 01/01: In groff source top directory add Emacs settings for most text files.

2014-09-03 Thread Keith Marshall
On 03/09/14 17:48, Keith Marshall wrote: > On 03/09/14 14:03, Bernd Warken wrote: >> But there are also some files with a timestamp: > > Honestly, it isn't worth worrying about; there are much more important > things to pursue, than this sort of trivia. And BTW, I also noticed that you changed th

Re: [Groff] [groff] 01/01: In groff source top directory add Emacs settings for most text files.

2014-09-03 Thread Keith Marshall
On 03/09/14 14:03, Bernd Warken wrote: > But there are also some files with a timestamp: > > config.guess:5:timestamp='2014-09-03' > ... > > config.sub:5:timestamp='2014-09-03' > ... > > configure:7928:"stamp-h":F) echo timestamp > stamp-h ;; > configure.ac:165:AC_CONFIG_FILES([stamp-h], [ec

Re: [Groff] [groff] 01/01: In groff source top directory add Emacs settings for most text files.

2014-09-03 Thread Bernd Warken
> Von: "Werner LEMBERG" > > > What about the mentioning of the `Last update'? > > Honestly, I think it should be dropped everywhere. It's a nuisance to > maintain, and people who are working from the git directly know what > they do... For everybody else, they can look up all changes in the >

Re: [Groff] [groff] 01/01: In groff source top directory add Emacs settings for most text files.

2014-09-03 Thread Werner LEMBERG
>> I suggest that in a range -, should be the year in >> which the particular file was created or added to the repository. >> should be updated every year and be identical everywhere. > > What about the mentioning of the `Last update'? Honestly, I think it should be dropped eve

Re: [Groff] wrong email adress for me

2014-09-03 Thread Ralph Corderoy
Hi Bernd, > I got several emails from the groff etc. mailing list. > The adress > bernd.war...@web.de # do not use this > is only for my private usage, not for groff. I think that's because people are replying to your git commits on the other list, http://lists.gnu.org/archive/html/groff-comm