In this post, "system" means groff/current/font/ and "local" means
/groff/site-font.
After implementing Robert G's advice that the contents of the system
/devps 'download' file be copied into the 'download' file in the local
/devps 'download', I decided to explore the matter further by
building th
On Saturday, 20 August 2022 01:05:02 BST Peter Schaffter wrote:
> In this post, "system" means groff/current/font/ and "local" means
> /groff/site-font.
Hi Peter,
"current" should be a symlink to a numbered version in the groff directory.
Where does it point on your system?
> After implementing
>
>
> All works fine here. I believe what hit Robert is that grops stops looking
> when it finds the first download file (which would be the one in site-font
> if
> it exists) which means that if there are any entries in the system
> download
> they would not be found. This is why copying those en
On Sunday, 21 August 2022 15:17:01 BST Robert Goulding wrote:
> If Deri says it looks for *all* the download files, then that must be
> correct! But is the manpage out of date then?
>
> Robert.
Hi Robert,
I have corrected it on git.
Cheers
Deri
commit 5b357550d90f59f4d37ae9f2ce3a562d97b78a01
Hi Deri,
At 2022-08-21T01:12:07+0100, Deri wrote:
> Gropdf is different, it takes into account all download files found,
> so there is no need to duplicate entries into the site-font download
> file. You could organise your fonts into separate families, each with
> its own separate download file j
Hi Branden,
> $download{"$foundry $name"}=$file;
...
> I think it _might_ be better to (a) perform that check (with the `-r`
> operator, I reckon), only adding $file to the hash if that succeeds
> and (b) skipping the validity check and hash update if the key
> ("$foundry $name") is al
Hi Ralph,
At 2022-08-21T17:43:03+0100, Ralph Corderoy wrote:
> How about making %download be a hash of lists and appending to the end
> of the relevant list without checking anything. Then run along the
> relevant list when the file is actually needed to find the first, if
> any, which opens. If
Deri --
Talk about diving down a rabbit hole and taking a wrong turn at
Albuquerque!
> If you look at gropdf around line 55, you should see something
> like:-
> $cfg{GROFF_VERSION}='1.22.4';
> $cfg{GROFF_FONT_PATH}='/usr/share/groff/site-font:/usr/share/groff/1.22.4/
> font:/usr/lib/font';
I lo
On Sunday, 21 August 2022 17:26:55 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2022-08-21T01:12:07+0100, Deri wrote:
> > Gropdf is different, it takes into account all download files found,
> > so there is no need to duplicate entries into the site-font download
> > file. You could organise y
Hi Branden,
> (B) I see a deviation from the GNU Coding Standards for diagnostic
> messages; we don't need a space after "troff:" when it's followed
> by a file name.
It seems much of the word doesn't comply
$ sed -f /etc/passwd
sed: file /etc/passwd line 3: extra characters afte
Hi Ralph, Branden,
On 8/22/22 10:04, Ralph Corderoy wrote:
Hi Branden,
(B) I see a deviation from the GNU Coding Standards for diagnostic
messages; we don't need a space after "troff:" when it's followed
by a file name.
It seems much of the word doesn't comply
$ sed -f /etc/p
Hi Alex,
At 2022-08-22T20:18:38+0200, Alejandro Colomar wrote:
> Also, I'd keep the space, even if only for being able to use standard
> tools like perror(3), or common tools like the functions.
Maybe I'm having a senior moment but I don't get what this has to do
with groff? groff rolls its own
Hi Branden,
On 8/23/22 00:08, G. Branden Robinson wrote:
Hi Alex,
At 2022-08-22T20:18:38+0200, Alejandro Colomar wrote:
Also, I'd keep the space, even if only for being able to use standard
tools like perror(3), or common tools like the functions.
Maybe I'm having a senior moment but I don'
13 matches
Mail list logo
