Hi Alex,
> +.TS
> +l lB lB l1 lX.
> +\& u64 flags; /* T{
> +.BR O_ *
> +flags */
> +T}
> +\& u64 mode; /* T{
> +Mode for
> +.BR O_ { CREAT , TMPFILE }
> +*/
> +T}
The inline font escapes, \fB...\fP, were much more readable because I
could still see, and check, the str
>> Perhaps it makes sense to execute
>>
>> ```
>> strace -f make &> strace.log
>> ```
>>
>> and check the resulting logfile for all file accesses outside of the
>> source and build directory, and whether they are expected.
>
> That's a good idea, if somewhat monstrous in its implications.
> Ther
At 2022-07-26T23:18:26+, Werner LEMBERG wrote:
> Perhaps it makes sense to execute
>
> ```
> strace -f make &> strace.log
> ```
>
> and check the resulting logfile for all file accesses outside of the
> source and build directory, and whether they are expected.
That's a good idea, if somewha
Hi Alex,
At 2022-07-26T21:33:07+0200, Alejandro Colomar wrote:
> I've already read all that was relevant to me from tbl(1) regarding
> what I had in mind: documenting structures.
Okay. Apart from those two nits I didn't get any other feedback from
you, did you find the document clear and satisfa
> I think the correct fix for this is to update the Automake files to
> set $GROFF_BIN_PATH to the build directory before running groff to
> generate our own artifacts. There are only a few directories that
> require this, all of which I think Ingo and/or I touched recently.
>
> Does that sound
[looping in groff@gnu]
Hi Werner,
At 2022-07-26T20:21:48+, Werner LEMBERG wrote:
> While building current git from groff (2f4432718c) with
>
> ```
> ./bootstrap --gnulib-srcdir=~/git/gnulib
> ./configure
> make -j12
> ```
>
> I got the following error messages:
>
> ```
> gropdf:contrib/mom
[looping in groff@]
Hi Werner!
At 2022-07-26T20:55:21+, Werner LEMBERG wrote:
> [2f4432718c50ac6cd59491366fb470f0d92f87ba]
>
> In file `groff.pdf`, starting with section 5.25, 'Drawing Requests',
> the quotation character in typewriter type used for the definition of
> escape sequences chang
I have managed to rescue my second message which was truncated!!
On Tuesday, 26 July 2022 17:19:04 BST Deri wrote:
> On Tuesday, 26 July 2022 09:00:25 BST joerg van den hoff wrote:
> > me again with an update/correction to the previous description of the
> > issue
> > (the described problem remain
I've managed to find the complete reply I sent!
On Tuesday, 26 July 2022 09:00:25 BST joerg van den hoff wrote:
> me again with an update/correction to the previous description of the issue
> (the described problem remains, though):
>
> 1.
> regarding the symobl fonts used by grops and gropdf I p
Format structures with tbl(1) to improve alignment in proportional-width font
text.
Reported-by: "G. Branden Robinson"
Signed-off-by: Alejandro Colomar
---
Hi Branden,
I feel this v3 is good enough to propose it as an actual patch to the list.
v3:
- Use .nf/.fi for comments, but not for typ
I must say that the source code is really ugly (ugly as in, someone
reading it will probably have a hard time modifying it, without reading
tbl(1)).
But at the same time, the result is beautiful, and the syntax is really
great. You can express exactly what you want.
Cheers,
Alex
On 7/26/2
Improved an v2 using T{...T} in combination with column modifiers and
removing .nf/.fi for the table, fixing a misplaced .PD, and .BR instead
of \fB...\fP:
open_how.2type: ffix
Format structures with tbl(1) to improve alignment in
proportional-width font text.
Reported-by: "G.
Thanks - It would take some work, I think, to make the character names
emitted by preconv match up with those in rfc1345 (but that maybe worth
doing as a comprehensive solution). In the past, I've simply redefined the
Greek letters one by one in just the way you suggested.
I see that the Slant is
Hi Branden,
I've already read all that was relevant to me from tbl(1) regarding what
I had in mind: documenting structures.
I haven't seen any mention to tables having a leading blank line, yet I
couldn't get rid of it without resorting to .PD.
Let me know if I'm doing something wrong, or i
Hi Robert,
At 2022-07-26T15:03:43-0400, Robert Goulding wrote:
> OK, this explains something that has puzzled me. I have installed
> fonts for Greek text, and while I get fine output from devps, when I
> generate a pdf directly through gropdf, all of the unaccented Greek
> characters come out slan
Hi Ralph,
On 7/26/22 14:25, Ralph Corderoy wrote:
Its long been the case that straying into undefined behaviour allows a
compiler to optimise away what is stated above as ‘almost certain’,
i.e. SIGSEGV.
http://blog.llvm.org/2011/05/what-every-c-programmer-should-know.html
Dereferenc
Hi Branden,
On 7/26/22 17:54, G. Branden Robinson wrote:
[...relocated material for a topic shift...]
+.SH NOTES
+The following headers also provide
+.BR NULL :
+.IR ,
+.IR ,
+.IR ,
+.IR ,
+.IR ,
+.IR ,
+and
+.IR .
Not exactly on topic (sorry), but apropos of our concurrent discussion
In light of the recent charges of regression and deviation laid against
me by Ingo and Ralph, I was amused to stumble across the following words
by James Clark from this 1991 commit to our (historically reconstructed)
Git repository.
diff --git a/PROBLEMS b/PROBLEMS
new file mode 100644
inde
Hi folks,
I've applied the advice from Deri and Dave appended below.
Updated docs, previewing groff 1.23, can be found at the same URL as
before.
https://www.dropbox.com/sh/17ftu3z31couf07/AAC_9kq0ZA-Ra2ZhmZFWlLuva?dl=0
Regards,
Branden
At 2022-07-25T16:20:34+0100, Deri wrote:
> The best of bo
[replying to groff@ from bug-groff@ so more people see this discussion]
I wanted to make sure more people saw this because Deri's explanation is
gold. I don't think there's any existing documentation that covers this
anywhere nearly as lucidly.
Regards,
Branden
At 2022-07-26T17:19:04+0100, Deri
Hi Alex,
I'm a bit late to the review party.
At 2022-07-26T14:48:01+0200, Alejandro Colomar wrote:
> diff --git a/man3const/NULL.3const b/man3const/NULL.3const
> new file mode 100644
> index 0..28a6f67aa
> --- /dev/null
> +++ b/man3const/NULL.3const
> @@ -0,0 +1,76 @@
> +.\" Copyright (c)
In an attempt to consolidate discussion about this that has heretofore
ranged far and wide, I've opened http://savannah.gnu.org/bugs/?62816.
It links to all previous discussions on the topic I could find; please
comment there if I've missed any, or if you have further thoughts that
aren't covered b
On 7/10/22, Bjarni Ingi Gislason wrote:
> I use stripped tmac files and "andoc.tmac" caused the bug in
> compatibility mode.
In the current code, to ("someday") be released as 1.23, not only is
stripping the tmac files no longer done, the script to do so was
removed entirely from the repository
Reported-by: "G. Branden Robinson"
Cc: Ralph Corderoy
Cc: Ingo Schwarze
Cc: Jakub Wilk
Signed-off-by: Alejandro Colomar
---
v2:
- Move to man3const [Ralph, Branden]
- Added LIBRARY section
- Added #include [Ralph]
- Note that it can also be used as a function pointer [Ralph]
- Document that
Hi Jakub,
On 7/25/22 20:57, Jakub Wilk wrote:
* Alejandro Colomar , 2022-07-24, 21:19:
+.B "#define NULL ((void *) 0)"
+.fi
+.SH DESCRIPTION
+.B NULL
+represents a null pointer constant.
+.PP
+According to POSIX,
+it shall expand to an integer constant expression with the value
+.B 0
+cast to
Hi Alex and Ingo,
Alex wrote:
> > > +It is undefined behavior to dereference a null pointer
> >
> > That is formally true, but hardly helpful in a manual page because
> > what happens when you dereference a NULL pointer is faily
> > predictable in practice: a segmentation fault.
> >
> > Any othe
Hi Ingo,
On 7/25/22 20:49, Ingo Schwarze wrote:
Hi Alejandro,
Alejandro Colomar wrote on Sun, Jul 24, 2022 at 09:19:32PM +0200:
- Move to man3const [Ralph, Branden]
- Added LIBRARY section
- Added #include [Ralph]
- Note that it can also be used as a function pointer [Ralph]
- Document that 0
27 matches
Mail list logo
