From: Tommy Kelly <tommy.kelly@verilab.com>
To: info-gnus-english@gnu.org
Subject: Hierarchical group names - component separator
Date: Mon, 03 Jan 2011 07:21:58 -0600 [thread overview]
Message-ID: <m2d3oe6s21.fsf@verilab.com> (raw)
Can anyone see a problem with using "/" us the separator of components
in a hierarchical group name. For example, instead of:
mylists.linkedin.updates
mylists.linkedin.groups.gnus
mylists.linkedin.groups.yaks
I'd use:
mylists/linkedin/updates
mylists/linkedin/groups/gnus
mylists/linkedin/groups/yaks
The reason is that gmail supports "folding" of the latter style. My
concern though is that somewhere deep in the current or planned lisp,
using "/" will break something.
If it's currently allowed, then maybe take this email as a pointing-out
of the fact that gmail *does* indeed support use of "/" and so it would
be nice if it remained allowed in the future :-)
Tommy
next reply other threads:[~2011-01-03 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 13:21 Tommy Kelly [this message]
2011-01-03 14:03 ` Tassilo Horn
2011-01-03 20:14 ` Tommy Kelly
[not found] <mailman.2.1294060939.32017.info-gnus-english@gnu.org>
2011-01-03 23:12 ` Lars Magne Ingebrigtsen
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=m2d3oe6s21.fsf@verilab.com \
--to=tommy.kelly@verilab.com \
--cc=info-gnus-english@gnu.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.
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).