From: Van L <van@scratch.space>
To: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: python.el and pydoc
Date: Thu, 11 Oct 2018 00:52:55 +1100 [thread overview]
Message-ID: <1C015ED4-2ECE-48BD-9D4E-F5A34D6C582B@scratch.space> (raw)
In-Reply-To: <jwvmurmou10.fsf-monnier+gmane.emacs.devel@gnu.org>
> (or has been over-written in the mean time)
A fossilizing approach avoids the distant future
reinventing a forgotten technique or wheel, tho.
prev parent reply other threads:[~2018-10-10 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 9:20 python.el and pydoc Sébastien Gendre
2018-08-21 13:36 ` Stefan Monnier
2018-10-10 0:03 ` Sébastien G.
2018-10-10 3:32 ` Eli Zaretskii
2018-10-10 12:40 ` Stefan Monnier
2018-10-10 13:52 ` Van L [this message]
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=1C015ED4-2ECE-48BD-9D4E-F5A34D6C582B@scratch.space \
--to=van@scratch.space \
--cc=emacs-devel@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.
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).