unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: emacs-devel@gnu.org
Subject: Emacs buglist old bugs are spamming me now  [FW: Undelivered Mail Returned to Sender]
Date: Tue, 16 Apr 2019 15:03:42 -0700 (PDT)	[thread overview]
Message-ID: <75d342ac-7178-4032-9881-d90c41cf31bf@default> (raw)

[-- Attachment #1: Type: text/plain, Size: 914 bytes --]

I've received over 50 messages like this so far today, out of the blue.

Each has an attachment with an old bug-list message (see attachments).

I'm hoping that someone is looking into this, or will do so.


-----Original Message-----
From: MAILER-DAEMON@linux-tuxedo.fritz.box <MAILER-DAEMON@linux-tuxedo.fritz.box> 
Sent: Tuesday, April 16, 2019 2:24 PM
To: Drew Adams <drew.adams@oracle.com>
Subject: Undelivered Mail Returned to Sender

This is the mail system at host linux-tuxedo.fritz.box.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<steve@localhost>: mail for localhost loops back to myself

[-- Attachment #2: Untitled.txt --]
[-- Type: message/delivery-status, Size: 369 bytes --]

[-- Attachment #3: Type: message/rfc822, Size: 1908 bytes --]

From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stephen.berman@gmx.net, emacs-devel@gnu.org
Subject: RE: emacs-25 f708cb2: Clarify doc string of 'transpose-sexps'
Date: Fri, 4 Nov 2016 12:36:32 -0700 (PDT)
Message-ID: <da4813cd-e7a6-49cc-9f80-7b89a60ab050@default>

> > It is really not great to tell someone they "cannot" or
> > "must not" etc. do something without raising an error that
> > really enforces "cannot" etc.
> 
> If someone comes up with a way to lift that restriction, we could
> remove this text from the doc string.  but as long as the command
> works as it does, I think we should document that, or else we will
> have bug reports about its not meeting expectations.

I did not suggest removing the text from the doc string.

The point is that it is better if the code backs up what
the doc says, by raising an error if you try to do what
it says you cannot do.

If `C-b' at bob did not raise an error, but instead just
moved point to the end of line 42, it would be scant help
to tell users in the doc of `C-b' that you cannot use it
at bob.

--A3C471301C7F.1555449819/linux-tuxedo.fritz.box--

             reply	other threads:[~2019-04-16 22:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 22:03 Drew Adams [this message]
2019-04-16 22:19 ` Emacs buglist old bugs are spamming me now [FW: Undelivered Mail Returned to Sender] Óscar Fuentes
2019-04-16 22:35   ` Óscar Fuentes
2019-04-16 23:13     ` Drew Adams
2019-04-17 19:31       ` Stephen Berman
2019-04-17 20:03         ` Drew Adams

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=75d342ac-7178-4032-9881-d90c41cf31bf@default \
    --to=drew.adams@oracle.com \
    --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).