From: Jude DaShiell <jdashiel@panix.com>
To: emacs-orgmode@gnu.org
Subject: orgmode bug capture procedure
Date: Mon, 6 Apr 2015 04:38:16 -0400 (EDT) [thread overview]
Message-ID: <alpine.NEB.2.11.1504060436020.23764@panix3.panix.com> (raw)
With a linux command that is defective, I can run script and get me a
typescript file to send to an author. Is that my best bet for capturing
an emacs-orgmode bug?
-- Twitter: JudeDaShiell
reply other threads:[~2015-04-06 8:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.NEB.2.11.1504060436020.23764@panix3.panix.com \
--to=jdashiel@panix.com \
--cc=emacs-orgmode@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 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.