From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>, Xebar Saram <zeltakc@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: reproducable orgmode edit crashes emacs..have backtrace..where to report?
Date: Fri, 09 Dec 2016 14:09:28 +0000 [thread overview]
Message-ID: <CAFyQvY2uC2f0E+_9AcFSXqBvDApC1LrwXM3hrD9x_0f7iVWKGQ@mail.gmail.com> (raw)
In-Reply-To: <871sxh8col.fsf@ucl.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
On Fri, Dec 9, 2016, 8:51 AM Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> On Friday, 9 Dec 2016 at 11:33, Xebar Saram wrote:
>
> Maybe using M-x report-emacs-bug RET?
>
Yup, filing a bug report is the best way in this case. Emacs is not
supposed to crash no matter what the user or any package does in the elisp
land.
M-x report-emacs-bug will also provide the devs with info like your emacs
version, which can be useful to debug this crash. Also provide a recipe in
that bug report on how to recreate that crash from an emacs -Q session. It
would be useful also to elaborate on what change you did you think started
these crashes to happen... Updating Emacs, updating org, both, or something
else?
> --
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1286 bytes --]
next prev parent reply other threads:[~2016-12-09 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f09b8664165248dd9690df77b3430bfb@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-12-09 13:16 ` reproducable orgmode edit crashes emacs..have backtrace..where to report? Eric S Fraga
2016-12-09 14:09 ` Kaushal Modi [this message]
2016-12-09 11:33 Xebar Saram
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY2uC2f0E+_9AcFSXqBvDApC1LrwXM3hrD9x_0f7iVWKGQ@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=zeltakc@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).