Dear Norwid,
On Wed, Mar 05, 2025 at 06:29:32PM +0100, Norwid Behrnd wrote:
> Dear Hans
>
> I'm able to locally replicate and compile the examples shared by you. Are the
> names of the bond types preliminary only?
Yes they are. Maybe a mere descriptive name would be more appropiate:
- dashed f
On Sun, Mar 9, 2025 at 11:03 AM G. Branden Robinson
wrote:
> it appears that "removing" characters may have never really worked,
> because the act of looking one up created it.
Do you have sample input that demonstrates this? Two simple
tests--using the "c" conditional, and attempting to use the
At 2025-03-10T14:57:24-0500, Dave Kemper wrote:
> On Sun, Mar 9, 2025 at 11:03 AM G. Branden Robinson
> wrote:
> > it appears that "removing" characters may have never really worked,
> > because the act of looking one up created it.
>
> Do you have sample input that demonstrates this?
I do not,
On Sunday, 9 March 2025 21:08:58 GMT Nikita Ivanov wrote:
> Hi Deri,
>
> Thank you! Yes, this solution is much easier than having to install
> fonts manually. Some questions and random findings/thoughts:
>
> It seems that it only works for PDF output, is there a similar simple
> solution for Post
On Sun, Mar 09, 2025 at 02:08:58PM -0700, Nikita Ivanov wrote:
> Hi Deri,
>
> Thank you! Yes, this solution is much easier than having to install
> fonts manually. Some questions and random findings/thoughts:
>
> It seems that it only works for PDF output, is there a similar simple
> solution for
On Sunday, 9 March 2025 10:51:41 GMT Nikita Ivanov wrote:
> Hello!
>
> I've been playing around with groff recently and once again discovered
> that there is a lot of friction involved if you want to use groff with
> Cyrillic characters (and probably other kinds of non-latin characters
> too).
>
Hi Deri,
Thank you! Yes, this solution is much easier than having to install
fonts manually. Some questions and random findings/thoughts:
It seems that it only works for PDF output, is there a similar simple
solution for PostScript?
Also, it was not completely friction-less for me because I had
On Fri, Mar 07, 2025 at 07:48:27PM +0100, Sigfrid Lundberg wrote:
> Thank you Thomas!
>
> I had already tried \p, but it is difficult to get it to work inside the
> refer support code in the macro packages used. It seems that such code has
> to be embedded in these strings overriding the ones that
Thank you Thomas!
I had already tried \p, but it is difficult to get it to work inside the
refer support code in the macro packages used. It seems that such code has
to be embedded in these strings overriding the ones that are in the macro
package you are using.
.ds ref*spec!A ", " "
.ds re
Le 2025-03-05 à 21:37, Sigfrid Lundberg a écrit :
So, now my questions have changed:
How do I make sure that a URL isn't hyphenated?
And how do I enforce a break using an escape sequence rather than .br?
You could use .nh to stop hyphenation and \p to break after the next word.
If you need t
Dear Doug and others,
I'm sorry. I added the altered scripts as attachment but
didn't realised that this will be added as text to the mail.
Will keep it in mind for a next time.
Kind regards,
Hans
On Tue, Mar 04, 2025 at 09:56:58AM -0500, Douglas McIlroy wrote:
> Please don't post huge programs
Please don't post huge programs (in this case 1500 lines) as email text.
For those of us who subscribe to the groff digest, it's a pain to scroll
past such monsters to see the remaining messages. Big documents are best
relegated to attachments, which readers who need them can fetch from the
mailin
e fourth below the drawing plane could simplify the drawing. Except when
> up to _explain_ Fischer formulae for carbohydrates.
>
> - Re tapered bonds/dashed bonds.
>
> Do you refer to _dashed bonds_ on one, and a _bold but non-tapered bond_ on
> an other stereogenic center o
Hi list,
Just another observation. This is mom-related.
While I need my headings to look like this in the corpus:
1 Introduction
2 Contextualization
2.1 Theme
2.2 General objective
References
Appendix A: Exemplary Flash games
But in the Table of Contents, I need to achieve the following:
1 I
/ train / test usage of CIP rules -- two
substituents and the (implicit) carbon in one layer, one substituent above,
the fourth below the drawing plane could simplify the drawing. Except when
up to _explain_ Fischer formulae for carbohydrates.
- Re tapered bonds/dashed bonds.
Do you refer to
Hello Deri,
Il 25 febbraio 2025 alle 20:49 Deri ha scritto:
> If you change it to:-
>
> .pdfhref W -D \\$[1] -- "\Z'\\$[2]'\v'0.25m'\D'l \w'\\$[2]'u 0'\v'-.25m'"
>
> You won't see the error. In the next version of groff this is not necessary,
> you don't need the "--".
many thanks, excellent!
On Tuesday, 25 February 2025 18:50:39 GMT Francesco Ariis wrote:
> Dear groff users,
>
> please help me diagnose a groff warning message.
>
> I have a macro to typeset clickable URLS as underlined:
>
> .de link
> .pdfhref W -D \\$[1] "\Z'\\$[2]'\v'0.25m'\D'l \w'\\$[2]'u 0'\v'-.25m'"
Il 23 febbraio 2025 alle 21:40 G. Branden Robinson ha scritto:
> You're doing some non-idiomatic things with the ms(7) package and the
> tbl(1) preprocessor.
>
> The ms package does not expect you to reconfigure the formatter's line
> length ad hoc within the document. Instead, if you require a
>
On Mon Feb 24, 2025 at 3:52 AM CET, G. Branden Robinson wrote:
> At 2025-02-24T03:36:28+0100, onf wrote:
> > On Mon Feb 24, 2025 at 2:36 AM CET, G. Branden Robinson wrote:
> > > [...]
> > > My lodestar on this point is that we can use C and the shell to create
> > > files named with trailing spaces
On Sun, Feb 23, 2025, Dave Kemper wrote:
> On Sun, Feb 23, 2025 at 9:41 PM G. Branden Robinson
> wrote:
> > You're getting into Bjarni territory here. (That's the groff
> > community's version of the Dunning-Kruger syndrome.)
> ...
> (I'm sending this to the list rather than privately not because
[self-follow-up]
At 2025-02-24T04:02:55-0600, G. Branden Robinson wrote:
> Anyone familiar with the discussions on this list of the
> conflation of adjustment and alignment in *roff will understand
> why the advice Bjarni offered was bad--it defeats the user's
> configuration of th
At 2025-02-23T23:34:36-0600, Dave Kemper wrote:
> On Sun, Feb 23, 2025 at 8:52 PM G. Branden Robinson
> wrote:
> > At 2025-02-24T03:36:28+0100, onf wrote:
> > > I think the point is that such filenames aren't being used,
> >
> > No, that's not "the point". It's _your_ point,
>
> Hey, originally
On Sun, Feb 23, 2025 at 8:52 PM G. Branden Robinson
wrote:
> At 2025-02-24T03:36:28+0100, onf wrote:
> > I think the point is that such filenames aren't being used,
>
> No, that's not "the point". It's _your_ point,
Hey, originally it was *my* point :-P
> > so breaking compatibility (and making
On Sun, Feb 23, 2025 at 9:41 PM G. Branden Robinson
wrote:
> Please refrain from offering advice in areas beyond your expertise, at
> least without admitting the same.
>
> You're getting into Bjarni territory here. (That's the groff
> community's version of the Dunning-Kruger syndrome.)
This com
At 2025-02-23T20:13:59+0100, onf wrote:
> Removing the -ms makes the issue disappear. The issue must originate
> in ms's definition of the TS macro,
No.
> since adding
> .ds TS
>
> at the beginning of the document fixes the issue even when -ms is
> included.
>
> By the way, your table data in
Hi Francesco,
At 2025-02-23T19:00:17+0100, Francesco Ariis wrote:
> a question about table width and line width.
>
> Attached is an MRE which displays my problem, which you can
> run with `groff -ms -t -Tpdf test.ms > out.pdf`
>
> In the document:
> 1. line width is set to 17cms
> 2. I inser
At 2025-02-24T03:36:28+0100, onf wrote:
> On Mon Feb 24, 2025 at 2:36 AM CET, G. Branden Robinson wrote:
> > [...]
> > My lodestar on this point is that we can use C and the shell to create
> > files named with trailing spaces, so there's no reason *roff, as a bona
> > fide programming language, sh
On Mon Feb 24, 2025 at 2:36 AM CET, G. Branden Robinson wrote:
> [...]
> My lodestar on this point is that we can use C and the shell to create
> files named with trailing spaces, so there's no reason *roff, as a bona
> fide programming language, shouldn't be capable as well--as long as it's
> not
At 2025-02-24T02:44:35+0100, onf wrote:
> On Mon Feb 24, 2025 at 1:09 AM CET, G. Branden Robinson wrote:
> > [...]
> > diff --git a/src/roff/troff/input.cpp b/src/roff/troff/input.cpp
> > index 2656ff236..cf750bc73 100644
> > --- a/src/roff/troff/input.cpp
> > +++ b/src/roff/troff/input.cpp
> > @@
On Mon Feb 24, 2025 at 1:09 AM CET, G. Branden Robinson wrote:
> [...]
> diff --git a/src/roff/troff/input.cpp b/src/roff/troff/input.cpp
> index 2656ff236..cf750bc73 100644
> --- a/src/roff/troff/input.cpp
> +++ b/src/roff/troff/input.cpp
> @@ -6405,12 +6405,14 @@ void line_file()
> {
>int n;
At 2025-02-23T23:52:07+0100, onf wrote:
> I would argue that the fact the second argument to lf is not used by
> groff to access the file system doesn't change its semantics of being
> a filename. Especially since soelim emits lf requests for all the .so
> calls it replaces, meaning that whatever
At 2025-02-23T17:23:35+0100, Benno Schulenberg wrote:
> > Regarding the hyphenation problem, the lump in the carpet moves
> > after groff 1.22.4. Because HTML output now produces −
> > entities rather than hyphens from *roff minus special characters
> > (`\-`), [...]
>
> Ouch! I don't like the l
On Sun Feb 23, 2025 at 11:38 PM CET, G. Branden Robinson wrote:
> At 2025-02-23T21:21:37+0100, onf wrote:
> > For all the other requests which use filenames (hpf, hpfa, lf -- am I
> > mistaken, or did we forget about lf? --, nx, so), it treats spaces as
> > an argument separator.
>
> No, I didn't f
At 2025-02-23T21:21:37+0100, onf wrote:
> For all the other requests which use filenames (hpf, hpfa, lf -- am I
> mistaken, or did we forget about lf? --, nx, so), it treats spaces as
> an argument separator.
No, I didn't forget about `lf`. See comment #0 ("original submission")
to Savannah #6510
On Sun Feb 23, 2025 at 1:50 PM CET, Dave Kemper wrote:
> On Sat, Feb 22, 2025 at 7:29 PM onf wrote:
> > I won't mind too much if this change ends up in groff as it's
> > currently being proposed. I would just find it unfortunate, because
> > I am pretty sure neatroff won't adopt it as it currently
Hi Benno,
On Sun Feb 23, 2025 at 5:23 PM CET, Benno Schulenberg wrote:
> > Regarding the hyphenation problem, the lump in the carpet moves after
> > groff 1.22.4. Because HTML output now produces − entities rather
> > than hyphens from *roff minus special characters (`\-`), [...]
>
> Ouch! I don
ion is to wait until someone fixes the bug in ms
you just discovered. A quick fix is to re-define the TS and TE
macros to do nothing, i.e.
.ds TS
.ds TE
~ onf
Hello Branden,
Regarding the hyphenation problem, the lump in the carpet moves after
groff 1.22.4. Because HTML output now produces − entities rather
than hyphens from *roff minus special characters (`\-`), [...]
Ouch! I don't like the look of them on the HTML page: they are
"enormous", loo
On Sat, Feb 22, 2025 at 7:29 PM onf wrote:
> I won't mind too much if this change ends up in groff as it's
> currently being proposed. I would just find it unfortunate, because
> I am pretty sure neatroff won't adopt it as it currently stands.
I'm in favor of cross-roff compatibility whenever pos
On Fri, Feb 7, 2025 at 3:06 AM G. Branden Robinson
wrote:
> At 2025-02-06T23:23:57-0600, Dave Kemper wrote:
> > The info file documents it the same way it documents everything else:
> > any attribute associated with an environment has this association
> > explicitly stated; attributes without this
By the way,
On Sun Feb 23, 2025 at 12:53 AM CET, G. Branden Robinson wrote:
> At 2025-02-22T23:23:35+0100, onf wrote:
> > If that's an accurate characterization, then please explain what that
> > NEWS file is about, because I don't get it.
>
> Again your references are too broad and too general.
Hi Dave,
On Sun Feb 23, 2025 at 12:59 AM CET, Dave Kemper wrote:
> On Sat, Feb 22, 2025 at 4:24 PM onf wrote:
> > The combination of points 1, 5, and 5b seems to imply that
> > .nx nx \" load file nx
> >
> > will be interpretted as loading file 'nx ' (without the quotes).
>
> Correct. I opened
Dear Branden,
On Sun Feb 23, 2025 at 12:53 AM CET, G. Branden Robinson wrote:
> [...]
> > It doesn't, because there is not a single line containing a comment
> > separated from the argument by a space. Read the examples I gave
> > above.
>
> I understand now. You are bewailing the removal of supp
On Sat, Feb 22, 2025 at 4:24 PM onf wrote:
> The combination of points 1, 5, and 5b seems to imply that
> .nx nx \" load file nx
>
> will be interpretted as loading file 'nx ' (without the quotes).
Correct. I opened http://savannah.gnu.org/bugs/?66673 in response to
this observation about the
Hi Branden,
[re-arranging]
On Sat Feb 22, 2025 at 9:37 PM CET, G. Branden Robinson wrote:
> At 2025-02-22T16:38:00+0100, onf wrote:
> [...]
> > I feel like changing ab, hpf, hpfa, nx, so, and tm (the others aren't
> > implemented by neatroff) to allow spaces in the middle
At 2025-02-22T16:38:00+0100, onf wrote:
> I forgot to emphasize the likely largest obstacle, which is the fact
> that it
(presumably Savannah #66625, and/or changes already in Git)
> would break compatibility with documents written for neatroff.
In what way?
> Ali seems averse to breaking backw
[self-reply; Benno not CCed]
At 2025-02-22T02:40:32-0600, G. Branden Robinson wrote:
> Hi Benno,
>
> I have some partial good news.
[...]
> I'm attaching HTML renderings with groff 1.23.0 and the bleeding edge.
For once I _didn't_ forget the attachments; I checked my Sent folder and
they're pres
On Sat Feb 22, 2025 at 4:46 AM CET, onf wrote:
> On Sat Feb 22, 2025 at 2:06 AM CET, G. Branden Robinson wrote:
> > if I follow through on Savannah #66625,
> > I mean to preserve traditional AT&T troff behavior of `tm` and `ab` in
> > compatibility mode, mainly because I can imagine people using `t
Il 21 febbraio 2025 alle 16:41 G. Branden Robinson ha scritto:
> Hi Francesco,
>
> At 2025-02-21T16:19:25+0100, Francesco Ariis wrote:
> > can I format/scale numbers when interpolating them?
>
> Not without arithmetic, as far as I know.
Thanks, my mind is at peace now that I know for sure!
Hi Benno,
I have some partial good news.
At 2025-02-17T11:52:27+0100, Benno Schulenberg wrote:
> Op 16-02-2025 om 15:13 schreef G. Branden Robinson:
> > > Is there a way to mark such long options in the man page so that
> > > browsers are prevented from breaking the marked text in any way?
> >
>
s (as they exist in groff Git's master
> > > branch).
> > >
> > > https://savannah.gnu.org/bugs/?66625
> >
> > Personally, I don't like how all of this breaks backwards
> > compatibility
[re-arranging]
> Combining your parenthetical with &qu
On Sat Feb 22, 2025 at 12:12 AM CET, G. Branden Robinson wrote:
> At 2025-02-21T15:22:02+0100, onf wrote:
> [...]
> > Ideally, `so` would behave like `tm` except it would trim spaces
> > at the end, but I understand that this would be adding yet another
> > special case.
>
> Alternatively, we could
At 2025-02-22T01:31:28+0100, onf wrote:
> On Sat Feb 22, 2025 at 12:12 AM CET, G. Branden Robinson wrote:
> > At 2025-02-21T15:22:02+0100, onf wrote:
> > [...]
> > > Ideally, `so` would behave like `tm` except it would trim spaces
> > > at the end, but I understand that this would be adding yet ano
On Sat Feb 22, 2025 at 12:21 AM CET, G. Branden Robinson wrote:
> At 2025-02-22T00:11:13+0100, onf wrote:
> > By the way, Heirloom troff has floating point registers.
>
> Just converting the type backing groff's registers from `int` to `long`
> is a significant refactor, because it implicates other
On Fri Feb 21, 2025 at 3:22 PM CET, onf wrote:
> Ideally, `so` would behave like `tm` except it would trim spaces
> at the end, but I understand that this would be adding yet another
> special case.
>
> Honestly, I never liked the fact `ds` doesn't trim trailing spaces.
> I never understood why the
At 2025-02-22T00:11:13+0100, onf wrote:
> By the way, Heirloom troff has floating point registers.
Just converting the type backing groff's registers from `int` to `long`
is a significant refactor, because it implicates other things like the
formatting of diagnostic messages. I found this out whe
At 2025-02-21T15:22:02+0100, onf wrote:
> On Fri Feb 21, 2025 at 3:14 PM CET, onf wrote:
> > Well, I have thought about it a bit since yesterday and I think
> > making `so` similar to `tm` would be a better idea:
> > $ 9 nroff << EOF
> > .tm Lorem ipsum dolor \" print to stderr
> > EOF
> >
On Fri Feb 21, 2025 at 11:41 PM CET, G. Branden Robinson wrote:
> I further observe that a loss of precision threatens.
>
> $ cat EXPERIMENTS/unit-conversion.groff
> .nf
> .nr basic-units-per-cm 1c
> There are \n[basic-units-per-cm] basic units per centimeter.
> The line length is \n[.l] basic unit
Hi Francesco,
At 2025-02-21T16:19:25+0100, Francesco Ariis wrote:
> can I format/scale numbers when interpolating them?
Not without arithmetic, as far as I know.
> Long explanation follows.
>
> While writing a minimal reproducible example for this list,
> I found myself typing:
>
> Lin
On Fri Feb 21, 2025 at 3:14 PM CET, onf wrote:
> Well, I have thought about it a bit since yesterday and I think making
> `so` similar to `tm` would be a better idea:
> $ 9 nroff << EOF
> .tm Lorem ipsum dolor \" print to stderr
> EOF
> Lorem ipsum dolor
Scrap that, I forgot to verify it's
On Fri Feb 21, 2025 at 4:39 AM CET, G. Branden Robinson wrote:
> At 2025-02-21T04:30:57+0100, onf wrote:
> [...]
> > Is my understanding correct that this change affects compatibility
> > mode too,
>
> Yes.
>
> > thus lessening compatibility with DWB troff?
>
> ...non sequitur. What is it that we'
At 2025-02-21T04:30:57+0100, onf wrote:
> On Fri Feb 21, 2025 at 2:27 AM CET, G. Branden Robinson wrote:
> > [...]
> > So in groff Git HEAD (actually, in Git for the past few months),
> > you've been able to do this:
> >
> > .so Planet "X".lrc
> >
> > ...whereas you could not in groff 1.23 and earl
Hi Branden,
On Fri Feb 21, 2025 at 2:27 AM CET, G. Branden Robinson wrote:
> [...]
> So in groff Git HEAD (actually, in Git for the past few months), you've
> been able to do this:
>
> .so Planet "X".lrc
>
> ...whereas you could not in groff 1.23 and earlier, or Heirloom Doctools
> troff, DWB 3.3
Hi Larry,
At 2025-02-20T16:49:47-0800, Larry McVoy wrote:
> On Thu, Feb 20, 2025 at 06:36:29PM -0600, G. Branden Robinson wrote:
> > At 2025-02-20T19:39:37+0100, onf wrote:
> > > On Thu Feb 20, 2025 at 5:59 PM CET, Douglas McIlroy wrote:
> > > > The idea that the argument of .so might contain unqu
On Thu, Feb 20, 2025 at 06:36:29PM -0600, G. Branden Robinson wrote:
> At 2025-02-20T19:39:37+0100, onf wrote:
> > On Thu Feb 20, 2025 at 5:59 PM CET, Douglas McIlroy wrote:
> > > The idea that the argument of .so might contain unquoted spaces is
> > > anathema--contrary to groff convention and for
At 2025-02-20T19:39:37+0100, onf wrote:
> On Thu Feb 20, 2025 at 5:59 PM CET, Douglas McIlroy wrote:
> > The idea that the argument of .so might contain unquoted spaces is
> > anathema--contrary to groff convention and fortunately not supported.
>
> As far as I know, .so currently doesn't support
On Thu, 20 Feb 2025, G. Branden Robinson wrote:
I think we Unix people lost this war, or at least need to write code
that is well-prepared to handle sojourns in foreign lands.
Yes. Sadly. Although some of us are lucky enough to mandate a file naming
policy within our own organization (and som
At 2025-02-20T15:55:40-0500, Steve Izma wrote:
> For what it's worth, I've always abhorred filenames with word spaces
> -- they usually require extra consideration in shell scripts and other
> programs.
Yes. I remember around 2002 or so when Apple released an iTunes update
that didn't appreciate
Thanks Branden,
That confirms my switch to putting the line range before the filename
rather than at the end, where it could be confused as part of the filename.
Cheers,
Neil
On Thu, 20 Feb 2025 at 00:21, G. Branden Robinson <
g.branden.robin...@gmail.com> wrote:
> At 2025-02-19T23:46:30+,
Indeed, .so does not keep a quoted argument together. Surely that's a bug.
Doug
On Thu, Feb 20, 2025 at 1:39 PM onf wrote:
> On Thu Feb 20, 2025 at 5:59 PM CET, Douglas McIlroy wrote:
> > The idea that the argument of .so might contain unquoted spaces is
> > anathema--contrary to groff conventi
On Thu, Feb 20, 2025 at 11:59:09AM -0500, Douglas McIlroy wrote:
> Subject: Re: idea for groff
>
> The idea that the argument of .so might contain unquoted spaces
> is anathema--contrary to groff convention and fortunately not
> supported. I think the idea of selecting lines from a
On Thu Feb 20, 2025 at 5:59 PM CET, Douglas McIlroy wrote:
> The idea that the argument of .so might contain unquoted spaces is
> anathema--contrary to groff convention and fortunately not supported.
As far as I know, .so currently doesn't support spaces even when quoted.
~ onf
> .so[2-11] /my/source/file with spaces in the name
The idea that the argument of .so might contain unquoted spaces is
anathema--contrary to groff convention and fortunately not supported. I
think the idea of selecting lines from a file is good, but it doesn't
warrant new groff syntax. I wou
On Thu Feb 20, 2025 at 2:05 AM CET, G. Branden Robinson wrote:
> I did the following interactively; a here document runs into escaping
> problems that I didn't want to mess with.
This might be useful (quoted from dash(1)):
The following redirection is often called a “here-document”.
[n]
On Wed, 19 Feb 2025, Larry McVoy wrote:
For the record, I like your way better.
.so[2-11] /my/source/file with spaces in the name
My opinion is what it is, but I'd prefer a .so[2-11] since it can be
backwards compat with .so /my/file.
I know that a '.so' allows spaces but I always di
At 2025-02-19T16:46:51-0800, Larry McVoy wrote:
> On Wed, Feb 19, 2025 at 11:46:30PM +, Neil Johnson wrote:
> > With my alternative syntax:
> >
> > .SO[2-11] /my/source/file
> > .SO[40-50] /my/source/file
> > .SO[...] /my/source/file
>
> I like this form. Though the o
On Wed, Feb 19, 2025 at 11:46:30PM +, Neil Johnson wrote:
> With my alternative syntax:
>
> .SO[2-11] /my/source/file
> .SO[40-50] /my/source/file
> .SO[...] /my/source/file
I like this form. Though the other way you could do it is
.SO /my/source/file\ with\
At 2025-02-19T23:46:30+, Neil Johnson wrote:
> That's actually where I started from as well! Except file names after
> the ".so" can have spaces in them on some platforms, and I don't
> believe there is a requirement to escape them, so something like this
> would be valid:
>
> .SO /my/
Thanks Damian,
That's actually where I started from as well! Except file names after
the ".so" can have spaces in them on some platforms, and I don't believe
there is a requirement to escape them, so something like this would be
valid:
.SO /my/source/file with spaces in the name.c
So the
On Wed, 19 Feb 2025, Neil Johnson wrote:
.so[2-11] /my/source/file.c
A long time ago, I did something like
.SO /my/source/file 2-11,40-50,...
and some variations which had a label to delimit sections.
Eventually, the reason for that disappeared and the sode for my special
soelim go
On Monday, 17 February 2025 22:22:46 GMT G. Branden Robinson wrote:
> [CCing groff@gnu list because some problems arise here that merit being
> findable by search of its list archives]
>
> Hi Deri,
>
> At 2025-02-17T18:52:46+, Deri wrote:
> > > programs in constructed pipeline:
> > >
>
[CCing groff@gnu list because some problems arise here that merit being
findable by search of its list archives]
Hi Deri,
At 2025-02-17T18:52:46+, Deri wrote:
> > programs in constructed pipeline:
> >
> > GNU grops (groff) version 1.23.0.2695-49927
> > GNU troff (groff) version
Hi Benno,
On Mon Feb 17, 2025 at 12:17 PM CET, Benno Schulenberg wrote:
> Op 16-02-2025 om 16:55 schreef onf:
> > Sounds like "modern" web browsers just break lines poorly. I have
> > replicated what you are describing in Firefox 128.7.0esr.
>
> I've checked that Dillo (3.0.5) does the same. And
In short, I would consider this to be a bug in the respective browsers.
Agreed. A hyphen should only be considered a hyphenatable position
when it has _alphabetical_ characters on both sides.
Reported here: https://bugzilla.mozilla.org/1948666
Benno
OpenPGP_signature.asc
Description:
Hi onf,
Op 16-02-2025 om 16:55 schreef onf:
Sounds like "modern" web browsers just break lines poorly. I have
replicated what you are describing in Firefox 128.7.0esr.
I've checked that Dillo (3.0.5) does the same. And epiphany (42.4)
too -- before it went into a tight spin and locked-up my
Hi Branden,
Op 16-02-2025 om 15:13 schreef G. Branden Robinson:
Is there a way to mark such long
options in the man page so that browsers are prevented from breaking
the marked text in any way?
Yes. It sounds like what you're looking for is the hyphenation control
escape sequence, `\%`.
I
> Hi Sebastian,
>
> I'm sorry it's taken a while to follow up with you.
No worries. It's a small and (somewhat) insignificant patch. I figured
someone would see it eventually, and even if they didn't, hopefully
anyone running into the issue I was facing would be able to find my post
when Google-in
At 2025-02-16T18:52:49-0400, Sebastien Peterson-Boudreau wrote:
> > Hi Sebastian,
> >
> > I'm sorry it's taken a while to follow up with you.
> No worries. It's a small and (somewhat) insignificant patch. I figured
> someone would see it eventually, and even if they didn't, hopefully
> anyone runn
[really, _really_, off-topic]
At 2025-02-16T19:53:41+0100, onf wrote:
> The problem with Graeber in general is that he is guided more by
> ideology than a honest search for truth.
Everyone who writes on matters "political" (as assessed by the entire
population, since a single voice suffices to br
Hi Branden,
On Sun Feb 16, 2025 at 4:19 AM CET, G. Branden Robinson wrote:
> At 2025-02-09T03:48:33+0100, onf wrote:
> > On Sun Feb 9, 2025 at 3:20 AM CET, onf wrote:
> > > [...]
> > > TL;DR:
> > > With the default settings, a tab essentially translates into a
> > > horizontal motion. [...]
> > >
At 2025-02-16T19:55:39+0100, onf wrote:
> By the way, I was asking for references to the passages of Old
> Testament you mentioned. (If I understood you correctly, that is.)
Oh. I have no fancy citation for that, just Leviticus 25:8-13, but I
got that from Wikipedia. Most of the Biblical literac
On Sun Feb 16, 2025 at 5:18 PM CET, G. Branden Robinson wrote:
> At 2025-02-16T16:46:44+0100, onf wrote:
> > > Surely this oversight has nothing to do with the ownership of most
> > > consumer debt [] by those occupying the commanding heights of our
> > > economies.
> >
> > Hm, that's really inter
On Sun Feb 16, 2025 at 5:18 PM CET, G. Branden Robinson wrote:
> At 2025-02-16T16:46:44+0100, onf wrote:
> > > Surely this oversight has nothing to do with the ownership of most
> > > consumer debt [] by those occupying the commanding heights of our
> > > economies.
> >
> > Hm, that's really inter
At 2025-02-16T16:46:44+0100, onf wrote:
> > Surely this oversight has nothing to do with the ownership of most
> > consumer debt [] by those occupying the commanding heights of our
> > economies.
>
> Hm, that's really interesting. Do you happen to have any sources to
> back this up?
While my rema
On Sun Feb 16, 2025 at 4:46 PM CET, onf wrote:
> I heard that they eventually modified the game by introducing the
> possibility that, from time to time (at random), your collaboration
> appears to the other player as defection (and vice versa) to model
> real world misunderstandings.
Not vice ver
Hi Benno,
On Sun Feb 16, 2025 at 12:04 PM CET, Benno Schulenberg wrote:
> In the HTML version of a man page it can happen that a long option
> (like --restricted) occurs near the right edge and that the browser
> splits the thing into "--" at the end of the line and "restricted"
> at the beginning
On Sun Feb 16, 2025 at 4:51 AM CET, G. Branden Robinson wrote:
> At 2025-02-16T04:37:46+0100, onf wrote:
> > > https://www.youtube.com/watch?v=BOvAbjfJ0x0
> >
> > Take note that (IIRC) the conclusion of research surrounding the
> > Prisoner's Dilemma has been that the best strategy is to reciproca
Hi Branden,
On Sun Feb 16, 2025 at 5:22 AM CET, G. Branden Robinson wrote:
> At 2025-02-10T18:23:14+0100, onf wrote:
> > Speaking of ignoring scale indicators, I wonder why `cs` still
> > ignores them in groff?
>
> I think for the same reason that they're ignored in the arguments to the
> `ss` req
Hi Benno,
At 2025-02-16T12:04:05+0100, Benno Schulenberg wrote:
> In the HTML version of a man page it can happen that a long option
> (like --restricted) occurs near the right edge and that the browser
> splits the thing into "--" at the end of the line and "restricted"
> at the beginning of the
Hi onf,
At 2025-02-10T18:23:14+0100, onf wrote:
> On Mon Feb 10, 2025 at 2:56 PM CET, Tadziu Hoffmann wrote:
> > > AT&T troff stores font size in points. This means it
> > > converts the argument to .ps from whatever unit it's in
> > > (default is points) to basic units and then divides that
> > >
1 - 100 of 4242 matches
Mail list logo
