From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, eggert@cs.ucla.edu, danielsutton01@gmail.com,
emacs-devel@gnu.org
Subject: Re: Sending bug reports without setting up email
Date: Wed, 11 May 2016 21:17:36 +0000 [thread overview]
Message-ID: <CAFyQvY3sV5oAqj3ri21mjksMGfsDg7nDeUV=LxpxK6K2xT+x1w@mail.gmail.com> (raw)
In-Reply-To: <8360ukb8zv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
On Wed, May 11, 2016 at 5:06 PM Eli Zaretskii <eliz@gnu.org> wrote:
> There's no need to do anything like that, report-emacs-bug already
> offers an alternative to put the entire message into the clipboard.
>
I believe you are referring to C-c M-i while in the *message* buffer? That
approach does not work for me as I copy the *message* buffer text across
VNC from linux to Windows to send email via Gmail. xdg-open/gvfs-open does
not work on the system where I run emacs.
--
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 807 bytes --]
next prev parent reply other threads:[~2016-05-11 21:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 13:50 Sending bug reports without setting up email Lars Ingebrigtsen
2016-05-09 18:19 ` Lars Ingebrigtsen
2016-05-09 18:52 ` Eli Zaretskii
2016-05-09 19:03 ` Lars Ingebrigtsen
2016-05-10 15:02 ` Paul Eggert
2016-05-11 20:55 ` daniel sutton
2016-05-11 21:00 ` Kaushal Modi
2016-05-11 21:05 ` Eli Zaretskii
2016-05-11 21:17 ` Kaushal Modi [this message]
2016-05-12 5:47 ` Eli Zaretskii
2016-05-11 21:01 ` Eli Zaretskii
2016-07-20 13:29 ` Lars Ingebrigtsen
2016-07-20 15:01 ` Paul Eggert
2016-07-20 15:06 ` Lars Ingebrigtsen
2016-07-20 16:07 ` Paul Eggert
2016-07-20 16:10 ` Lars Ingebrigtsen
2016-07-20 16:27 ` Paul Eggert
2016-07-20 16:30 ` Lars Ingebrigtsen
2016-07-20 16:37 ` Stefan Monnier
2016-07-21 10:45 ` Lars Ingebrigtsen
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='CAFyQvY3sV5oAqj3ri21mjksMGfsDg7nDeUV=LxpxK6K2xT+x1w@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=danielsutton01@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 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.