unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "T.V Raman" <raman@google.com>
Cc: adam@alphapapa.net, emacs-devel@gnu.org, dgutov@yandex.ru,
	joaotavora@gmail.com, stefankangas@gmail.com
Subject: Re: Better way to require with shorthands/renamed symbols
Date: Thu, 30 Sep 2021 02:04:28 -0400	[thread overview]
Message-ID: <E1mVpBE-0001p7-LZ@fencepost.gnu.org> (raw)
In-Reply-To: <p91o88dwjm5.fsf@google.com> (raman@google.com)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Consider a prefix separator char like ':' so that the shorthand is
  > easily distinguishable as a shorthand prefix? Might help in many ways:

We plan to use this for existing prefixes that do not have a colon.
For instance, 's-'.

 
-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2021-09-30  6:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210927003203.15806.29864@vcs0.savannah.gnu.org>
     [not found] ` <20210927003205.EF26620A5E@vcs0.savannah.gnu.org>
2021-09-27 11:10   ` Better way to require with shorthands/renamed symbols Stefan Kangas
2021-09-27 11:58     ` Dmitry Gutov
2021-09-27 12:54       ` Shorthands have landed on master (Was: Better way to require with shorthands/renamed symbols) João Távora
2021-09-27 13:06         ` Dmitry Gutov
2021-09-27 22:40         ` Shorthands have landed on master Philip Kaludercic
2021-09-27 22:58           ` João Távora
2021-09-28  7:15             ` Philip Kaludercic
2021-09-28  9:03               ` João Távora
2021-09-28  9:14                 ` Eli Zaretskii
2021-09-28  9:17                   ` João Távora
2021-09-28  9:22                 ` Philip Kaludercic
2021-09-28 23:37         ` Shorthands have landed on master (Was: Better way to require with shorthands/renamed symbols) Richard Stallman
2021-09-27 12:24     ` Better way to require with shorthands/renamed symbols João Távora
2021-09-27 12:55       ` Dmitry Gutov
2021-09-27 13:09         ` João Távora
2021-09-27 15:05           ` Stefan Kangas
2021-09-27 16:59             ` João Távora
2021-09-27 20:12               ` Stefan Kangas
2021-09-27 20:18                 ` João Távora
2021-09-28  1:53                   ` T.V Raman
2021-09-30  6:04                     ` Richard Stallman [this message]
2021-09-28  4:01                 ` Ihor Radchenko

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1mVpBE-0001p7-LZ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=adam@alphapapa.net \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=raman@google.com \
    --cc=stefankangas@gmail.com \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).