From: Aaron Schrab <aaron@schrab.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Ahmad Ismail <ismail783@gmail.com>,
Lewis Butler <lbutler@covisp.net>, Zsh Users <zsh-users@zsh.org>
Subject: Re: How to refer to other mails (was: Re: completely disable zsh completion system)
Date: Fri, 4 Sep 2020 18:02:50 -0400 [thread overview]
Message-ID: <20200904220250.GB1014@pug.qqx.org> (raw)
In-Reply-To: <20200904185656.77773e38@tarpaulin.shahaf.local2>
At 18:56 +0000 04 Sep 2020, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> (The message number is a standard feature of MLMs,
I'd definitely disagree about that being standard. The only MLM I'm
aware of which provides that is ezmlm, at least as far as a message
number being visible in the copies received by subscribers. Web archives
created by Mhonarc (used by Mailman 2, as well as Debian lists, and
likely others) include a message number in the URL for individual
messages. But that's not visible outside of the web archive, it's also
not stable if the web archive is regenerated from the raw messages.
I subscribe to quite a few mailing lists handled by a number of
different MLM systems; none of those lists, outside of zsh-related ones,
includes a message number.
next prev parent reply other threads:[~2020-09-04 22:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 13:13 completely disable zsh completion system Ahmad Ismail
2020-08-26 13:24 ` Roman Perepelitsa
2020-08-26 13:30 ` Ahmad Ismail
2020-08-26 13:40 ` Roman Perepelitsa
2020-08-26 13:45 ` Ahmad Ismail
2020-08-28 3:05 ` Daniel Shahaf
2020-08-28 6:22 ` Lewis Butler
2020-09-04 16:27 ` Ahmad Ismail
2020-09-04 18:56 ` How to refer to other mails (was: Re: completely disable zsh completion system) Daniel Shahaf
2020-09-04 22:02 ` Aaron Schrab [this message]
2020-09-04 23:27 ` Daniel Shahaf
2020-09-05 11:30 ` Ahmad Ismail
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200904220250.GB1014@pug.qqx.org \
--to=aaron@schrab.com \
--cc=d.s@daniel.shahaf.name \
--cc=ismail783@gmail.com \
--cc=lbutler@covisp.net \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).