unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs documentation is bad
Date: Sun, 9 Sep 2018 23:22:13 +0200	[thread overview]
Message-ID: <20180909212213.GA28530@tuxteam.de> (raw)
In-Reply-To: <8736uie5rh.fsf@bsb.me.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Sep 09, 2018 at 10:10:42PM +0100, Ben Bacarisse wrote:

[...]

> I get the feeling you don't really want an explanation!  But I decided
> to post this anyway because other reader might be interested and it
> helps to keep the archive clear on unanswered questions.

Your patience is exemplary. Thanks, Ben :)

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluVjwUACgkQBcgs9XrR2kZRsQCbBlzxrDQIlzygxRgC3avzbpBb
FJIAniQ18VASK5k2BWFO+mAXCVlsw4/I
=rCqg
-----END PGP SIGNATURE-----



  reply	other threads:[~2018-09-09 21:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-09  1:46 Emacs documentation is bad John Stone
2018-09-09  1:48 ` John Stone
2018-09-09  1:49   ` John Stone
2018-09-09 13:34     ` tomas
2018-09-09 14:26       ` John Stone
2018-09-10  4:13         ` Bob Newell
2018-09-10  8:54           ` Van L
     [not found]         ` <mailman.577.1536552821.1284.help-gnu-emacs@gnu.org>
2018-09-12 20:06           ` Emanuel Berg
2018-09-12 22:08           ` Emanuel Berg
     [not found]       ` <mailman.555.1536503215.1284.help-gnu-emacs@gnu.org>
2018-09-09 21:33         ` Barry Fishman
2018-09-09 21:39           ` Noam Postavsky
     [not found]           ` <mailman.570.1536529199.1284.help-gnu-emacs@gnu.org>
2018-09-09 22:10             ` Barry Fishman
     [not found]   ` <mailman.548.1536497190.1284.help-gnu-emacs@gnu.org>
2018-09-09 21:10     ` Ben Bacarisse
2018-09-09 21:22       ` tomas [this message]
2018-09-09 21:38       ` Barry Fishman

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=20180909212213.GA28530@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).