From: Drew Adams <drew.adams@oracle.com>
To: Paul Pogonyshev <pogonyshev@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: RE: Edebug: avoid messages on 'f' command
Date: Fri, 6 May 2016 10:32:12 -0700 (PDT) [thread overview]
Message-ID: <fdcad1ba-b0a2-4847-90fe-6480e2120362@default> (raw)
In-Reply-To: <CAG7BpapM+3mNshT-=9CLpv1vxpYMLE9nYM8yobjrF1dPzujYLQ@mail.gmail.com>
> I just know now it's pointless to use M-x report-emacs-bug
> unless you use Emacs to handle your mail in general.
FWIW - I use `M-x report-emacs-bug', and I don't let Emacs
handle my mail - at all.
For me, `M-x report-emacs-bug' works well. My mail client
is MS Outlook. I use `M-x report-emacs-bug' to compose the
message and record session information (e.g. Emacs build).
Then I use `C-c C-c' and paste the copied message into a new
mail-client message that pops up, addressed and ready to send.
Easy.
next prev parent reply other threads:[~2016-05-06 17:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 18:58 Edebug: avoid messages on 'f' command Paul Pogonyshev
2016-05-05 13:10 ` Alan Mackenzie
2016-05-05 21:44 ` Paul Pogonyshev
2016-05-06 10:52 ` Paul Pogonyshev
2016-05-06 12:11 ` Clément Pit--Claudel
2016-05-06 12:51 ` Eli Zaretskii
2016-05-06 14:25 ` Paul Pogonyshev
2016-05-06 15:01 ` Eli Zaretskii
2016-05-06 15:03 ` Kaushal Modi
2016-05-06 17:09 ` Paul Pogonyshev
2016-05-06 17:16 ` Kaushal Modi
2016-05-06 17:32 ` Drew Adams [this message]
2016-05-07 6:57 ` Alan Mackenzie
2016-05-07 11:55 ` Paul Pogonyshev
2016-05-07 13:40 ` Kaushal Modi
2016-05-07 13:45 ` Kaushal Modi
2016-05-07 13:54 ` Kaushal Modi
2016-05-07 18:40 ` Richard Stallman
2016-05-07 19:08 ` Alan Mackenzie
2016-05-09 13:55 ` Marcin Borkowski
2016-05-09 15:18 ` Paul Pogonyshev
2016-05-07 14:21 ` Eli Zaretskii
2016-05-07 17:17 ` Alan Mackenzie
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=fdcad1ba-b0a2-4847-90fe-6480e2120362@default \
--to=drew.adams@oracle.com \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pogonyshev@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.