Hi Ralph,
Ralph Corderoy wrote on Fri, Mar 25, 2022 at 12:42:02PM +:
> Adding SPF can normally be done without much disruption and will help
> the reputation of emails from usta.de.
> https://en.wikipedia.org/wiki/Sender_Policy_Framework
It's a feature that you can use varying mail servers t
Quoth G. Branden Robinson:
Thank you for clarifying. I don't have any Plan 9 source artifacts from
that far back; I use "n-t-roff"'s GitHub repository, for which the first
commit is dated 12 October 2014.
A cursory Google search did not turn up downloadable source archives of
any release prior
Quoth G. Branden Robinson:
Hah--if I had just read all the way to the bottom of the message I'd
cited, I would have found a working link to archives for all 4 (+1)
editions of Plan 9. Good show on the Plan 9 Foundation.
Hah—if I had just read all the messages in this thread before replying,
I
Hi,
John Gardner wrote:
> > GMail did the exact same thing to me with the same 3 emails from
> > Ingo. His messages since then _seem_ to have gotten to me reliably.
>
> I recently had to add a Gmail filter to mark e-mails from Ingo as
> *NOT* spam.
Adding SPF can normally be done without much di
[I said:]
> A cursory Google search did not turn up downloadable source archives
> of any release prior to the fourth edition, though it appears there
> should be no legal impediment to their distribution[1].
[...]
> [1] https://marc.info/?l=9fans&m=161650489113326
Hah--if I had just read all the
Ho humm,
At 2022-03-25T09:17:59+, Humm wrote:
> Quoth G. Branden Robinson:
> > As far as I know, groff innovated these character definitions, and my
> > hat's off to James Clark for doing so. Lacking them for so long strikes
> > me as...blinkered.
>
> When was that? In the git commit messag
Quoth G. Branden Robinson:
As far as I know, groff innovated these character definitions, and my
hat's off to James Clark for doing so. Lacking them for so long strikes
me as...blinkered.
When was that? In the git commit messages I see it in 2000.
\(dq appears in the first edition of Plan 9
On Fri, 25 Mar 2022, John Gardner wrote:
Since Gmail's *"Report as not-spam"* function appears to be doing fuck all,
I recommend every other Gmail user do something similar to this:
FWIW, Trend's Hosted Email Gateway does not mark Ingo's stuff as spam.
Stay safe - Damian
Pacific Engineering
> GMail did the exact same thing to me with the same 3 emails from Ingo.
> His messages since then _seem_ to have gotten to me reliably.
I recently had to add a Gmail filter to mark e-mails from Ingo as *NOT*
spam. He e-mailed me again recently and I nearly missed it under the usual
deluge of bull
At 2022-03-20T19:25:30+0100, Alejandro Colomar (man-pages) wrote:
> Hi Ingo,
>
> On 3/20/22 10:48, Ingo Schwarze wrote:
> > Hi Alex,
> It seems your emails didn't reach me directly.
> But the email from the mailing list arrived to my other mailbox.
> Hummm.
>
> After that, I checked again, and I
Hi Ralph,
At 2022-03-21T10:24:06+, Ralph Corderoy wrote:
> Hi Branden,
>
> > At 2022-03-20T10:48:56+0100, Ingo Schwarze wrote:
> > > > When a double-quoted word is not space-separated from an adjacent
> > > > word, it's not considered a different argument _except_ if if is
> > > > the first a
> Alejandro Colomar (man-pages) wrote:
>
> On 3/20/22 10:36, G. Branden Robinson wrote:
>> Yes, something about this should become part of groff(7). In
>> groff_man_style(7), I have restricted the discussion to advising people
>> to use the \(dq special character (also spellable as \[dq]).
>
Hi Branden,
> At 2022-03-20T10:48:56+0100, Ingo Schwarze wrote:
> > > When a double-quoted word is not space-separated from an adjacent
> > > word, it's not considered a different argument _except_ if if is
> > > the first argument.
> >
> > That description is inaccurate. It has nothing to do wi
Hi Ingo,
On 3/20/22 10:48, Ingo Schwarze wrote:
> Hi Alex,
It seems your emails didn't reach me directly.
But the email from the mailing list arrived to my other mailbox.
Hummm.
After that, I checked again, and I found your email in the SPAM folder...
#$%* gmail!
> Alejandro Colomar (man-pages)
At 2022-03-20T10:48:56+0100, Ingo Schwarze wrote:
> > When a double-quoted word is not space-separated from an adjacent
> > word, it's not considered a different argument _except_ if if is the
> > first argument.
>
> That description is inaccurate. It has nothing to do with whether
> or not it is
Hi, Branden!
On 3/20/22 10:36, G. Branden Robinson wrote:
> At 2022-03-20T01:29:32+0100, Alejandro Colomar (man-pages) wrote:
> Ralph's description, as I parse it, is correct. I'll speak to the
> broader issue of documentation coverage of the matter.
>
>> Could you please improve the documentati
At 2022-03-20T12:59:38+0100, Ingo Schwarze wrote:
> But since modern manual pages are mostly written and maintained
> by people used to younger languages, i still think the following
> advice is useful to avoid confusion of modern manual page maintainers:
> If you quote a macro argument, always pro
Hi Ralph,
On 3/20/22 09:32, Ralph Corderoy wrote:
> Hi Alex,
>
> - If an argument starts with a " then it ends at the next " which isn't
> the start of a "" or at the end of the line if there isn't a single ".
> - If an argument does not start with a " then the " within it are
> literal and t
Hi Ralph,
Ralph Corderoy wrote on Sun, Mar 20, 2022 at 10:06:14AM +:
> Ingo Schwarze wrote:
>> but the roff(7) manual in the mandoc package says this:
> ...
>> Leaving out the terminating double quote character at the end of
>> the line is discouraged.
> I think that's idiomatic and
Hi Ingo,
> but the roff(7) manual in the mandoc package says this:
...
> Leaving out the terminating double quote character at the end of
> the line is discouraged.
I think that's idiomatic and an early thing one learns about troff's
‘strings’ compared to programming languages in order to
Hi Alex,
Alejandro Colomar (man-pages) wrote on Sun, Mar 20, 2022 at 01:29:32AM +0100:
> I've met some undocumented (or I couldn't find it) behavior
> of double quotes ("),
I did not check the authoritative GNU troff documentation yet,
but the roff(7) manual in the mandoc package says this:
M
At 2022-03-20T01:29:32+0100, Alejandro Colomar (man-pages) wrote:
> Hi Branden,
>
> I've met some undocumented (or I couldn't find it) behavior of double
> quotes ("), which might be a bug in groff(1):
Hi Alex!
Ralph's description, as I parse it, is correct. I'll speak to the
broader issue of d
Hi Alex,
- If an argument starts with a " then it ends at the next " which isn't
the start of a "" or at the end of the line if there isn't a single ".
- If an argument does not start with a " then the " within it are
literal and the argument ends just before the next space or the end of
the
Hi Branden,
I've met some undocumented (or I couldn't find it) behavior of double
quotes ("), which might be a bug in groff(1):
$ cat arg.7
.TH foo 7 foo foo foo
.SH Test
.IR "foo"bar
.IR foo"bar"
.IR "foo"bar"baz"
$ man ./arg.7 | cat
foo(7) foofo
24 matches
Mail list logo
