all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Dedicated window for *log-edit-files*
Date: Fri, 25 Oct 2019 12:48:19 +0100	[thread overview]
Message-ID: <CALDnm506ye+Lnxn0rFSw3ydv-sKq-OBa4OPirosvWFbJsELYdQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

When finalizing a commit with VC, (I usually do it from vc-next-action
but maybe there are other ways), a buffer and a window popup for
*log-edit-files*, showing the files touched by the "commit" (here
I'm using "commit" to designate the corresponding VC action
across VCSystems).

For me personally, the window is quite annoying because it's
in the path of my "C-x o" workflow: very frequently I want to jump
back to the source buffer to do some last minute adjustment.

My questions are:

1. can I get rid of the `*log-edit-files*` window & buffer?
1.2. what about just the window?
2. does the buffer serve any other purpose besides
informing me?
3. supposing the answer to 2 is "No" would some
overlay text in the *vc-log* buffer, much like the overlay
trickery that is already done there, server the same
purpose?

Would a patch that does 3 be acceptable?

João

[-- Attachment #2: Type: text/html, Size: 1442 bytes --]

             reply	other threads:[~2019-10-25 11:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 11:48 João Távora [this message]
2019-10-25 12:48 ` Dedicated window for *log-edit-files* Stefan Monnier
2019-10-25 15:36   ` João Távora
2019-10-25 15:50     ` Stefan Monnier
2019-10-25 21:38       ` João Távora
2019-10-25 23:51         ` Stefan Monnier
2019-10-29 21:37     ` Juri Linkov
2019-10-25 14:43 ` Drew Adams
2019-10-25 15:21   ` João Távora
2019-10-26  8:12 ` martin rudalics
2019-10-26 12:00   ` Stefan Monnier
2019-10-27  7:49     ` martin rudalics
2019-10-27 17:43       ` Stefan Monnier

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=CALDnm506ye+Lnxn0rFSw3ydv-sKq-OBa4OPirosvWFbJsELYdQ@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=emacs-devel@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.