unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Gemini Lasswell <gazally@runbox.com>
Cc: emacs-devel@gnu.org
Subject: Re: backtrace-mode
Date: Wed, 20 Jun 2018 18:23:17 +0300	[thread overview]
Message-ID: <m2y3f9zdlm.fsf@fgunbin.playteam.ru> (raw)
In-Reply-To: <871sd2mli3.fsf@runbox.com> (Gemini Lasswell's message of "Tue, 19 Jun 2018 15:58:44 -0700")

On 19/06/2018 15:58 -0700, Gemini Lasswell wrote:

> - Now that xref-find-definitions works in backtrace buffers, I think
>   it would be better to stop making buttons for the functions in a
>   backtrace, and to document M-. as the best way to jump to function
>   definitions from backtraces.  What do you think of this change to
>   existing behavior, with or without a new customization variable to
>   preserve the old behavior?

I'd rather have buttons as well.

> - Tab and backtab are used by button navigation.  Seems to me the next
>   best choice for bindings for pretty printing and collapsing back to
>   one line are '+' and '-' except '-' is bound to negative-argument
>   in special-mode.  So I'm currently using '+' and '=', but I don't
>   like the '='.  Would it be ok to rebind '-' in backtrace buffers?

Maybe something with `-e' for expand and `-c' for collapse, like
`C-c'/`C-e' in outline-mode?

Filipp



      parent reply	other threads:[~2018-06-20 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19 22:58 backtrace-mode Gemini Lasswell
2018-06-20  5:52 ` backtrace-mode Helmut Eller
2018-06-22  0:08   ` backtrace-mode Gemini Lasswell
2018-06-22  2:07     ` backtrace-mode Stefan Monnier
2018-06-22  5:41       ` backtrace-mode Gemini Lasswell
2018-06-20 12:32 ` backtrace-mode Stefan Monnier
2018-06-20 15:23 ` Filipp Gunbin [this message]

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=m2y3f9zdlm.fsf@fgunbin.playteam.ru \
    --to=fgunbin@fastmail.fm \
    --cc=emacs-devel@gnu.org \
    --cc=gazally@runbox.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.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).