Hi Damian,
> echo "$i" | sed -e 's%[[./*$^\\]%\\&%g' -e 's%.*%/^&:/d%'
...
> sed: -e expression #1, char 18: unterminated `s' command
It's the first expression which is the problem.
$ sed -e 's%[[./*$^\\]%\\&%g'
I have a version of vgrind with the line
echo "$i" | sed -e 's%[[./*$^\\]%\\&%g' -e 's%.*%/^&:/d%'
It has worked for a gazillion years - 20+.
Upon upgrading to CentoS 7.9, I suddently find that I get an error
sed: -e expression #1, char 18: unterminated `s' command
Can anybo
On Saturday, 24 December 2022 01:26:22 GMT Richard Morse wrote:
> > I've been curious: how much use do you see of groff outside of man pages?
>
> I realize I’m just one person, but my use of groff (and Heirloom for using
> useful fonts) is entirely outside of man pages…
>
> Ricky
At the start of
* On 2022 24 Dec 16:45 -0600, Russ Allbery wrote:
> "G. Branden Robinson" writes:
> > At 2022-12-23T12:49:15-0800, Russ Allbery wrote:
>
> >> I've been curious: how much use do you see of groff outside of man
> >> pages?
About 18 months ago I received some good help on this list for setting
up s
On Saturday, 24 December 2022 17:31:38 GMT Steffen Nurpmeso wrote:
> "o" for the former.
> 'That said, https://ftp.sdaoden.eu/code-mailx-1.pdf (beware:
> 1MB!), realized with newest minor of mdocmx on groff
> 1.23.0.rc1.2915-c6d7, via pdfmark.tmac, causes the outline pane to
> show things twice; i
Snipping most of this message, as it's stuff where either I agree or
no response seems necessary.
On 12/13/22, G. Branden Robinson wrote:
>> Still, as long as the release notes mention the default line-length
>> change, I think we're covered. It looks like the relevant NEWS item
>> mentions that
Hi All,
On 23/12/2022 21:49, Russ Allbery wrote:
I've been curious: how much use do you see of groff outside of man pages?
Well, I've never written a single man page with the man macro set. I
have to confess, though, that during the early 1990s I wrote software
for MSDOS (that was the only pl
"G. Branden Robinson" writes:
> At 2022-12-23T12:49:15-0800, Russ Allbery wrote:
>> I've been curious: how much use do you see of groff outside of man
>> pages?
> Others have answered this but I would also point you to Ralph Corderoy's
> page on the subject.
> https://www.troff.org/pubs.html
>
On Saturday, 24 December 2022 09:06:07 GMT Ralph Corderoy wrote:
> Hi Deri,
>
> > You may need to open the outline pane on the left, which acts like a
> > table of contents.
>
> Is it mandatory that a PDF viewer must supply this mechanism to be
> worthy of the name? Off-hand, I don't recall mupd
Ralph Corderoy wrote in
<20221224090607.7dbb222...@orac.inputplus.co.uk>:
|Hi Deri,
|
|> You may need to open the outline pane on the left, which acts like a
|> table of contents.
|
|Is it mandatory that a PDF viewer must supply this mechanism to be
|worthy of the name? Off-hand, I don't r
"G. Branden Robinson" writes:
> These are all correct statements.
> There are two major points to make here.
> 1. Request invocations are not macro calls. So all that stuff about
> double quotes we were talking about doesn't apply here. :(
> Sorry about that. That was a language des
"G. Branden Robinson" writes:
> At 2022-12-23T10:03:13-0800, Russ Allbery wrote:
>> Yeah, the difficulty lies mostly in the layering, because people can
>> write POD source that is nonsensical in a man page context but that I
>> still have to do something with. Stuff like C<<< B<< L >> >>>.
> T
Hi Deri,
> You may need to open the outline pane on the left, which acts like a
> table of contents.
Is it mandatory that a PDF viewer must supply this mechanism to be
worthy of the name? Off-hand, I don't recall mupdf(1) or llpp(1) having
an option or keystroke to show it.
--
Merry Christmas
13 matches
Mail list logo
