unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Hopkins <emacs@unbit.co.uk>
To: 65245@debbugs.gnu.org
Subject: bug#65245: Possible code removal in eshell/diff (em-unix.el)
Date: Sat, 12 Aug 2023 11:49:56 +0100	[thread overview]
Message-ID: <00c46fb4ab8972714de3d338acbd5040@unbit.co.uk> (raw)

Hi,
I think the use of `compilation-finish-functions' and
#'current-window-configuration can be removed from #'eshell/diff
as it's no longer called and the intended functionality is achieved
elsewhere.

For example the below works with/without the 
`compilation-finish-functions'.

   $ emacs -Q -f eshell
   # in the eshell buffer
   echo a > a
   echo b > b
   diff -u a b
   # pops a #'diff-mode window with font-lock enabled; press q to quit

Here are some commits showing the introduction and then others
that help make it no longer relevant.

2001-04-24 ef59cfc6638a8ac3fccbee88482d142e95c32f81
	   Use `compilation-finish-functions' in #'eshell/diff

2004-02-02 c010ecfa9a26549486bb00c39221813c02c615de
            Bind q to #'quit-window in `diff-mode-shared-map'

2004-02-11 540d066630c55ab957dc08aa7abbca7775c9bd7b
	   #'diff - don't use compile any more, use diff-mode instead.

2011-02-01 abef340a0c5304054a2a5e6d95e1d825501f0e7a
	   `diff-mode-shared-map' inherit from `special-mode-map'

Best,
Richard





             reply	other threads:[~2023-08-12 10:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12 10:49 Richard Hopkins [this message]
2023-08-13 13:18 ` bug#65245: Possible code removal in eshell/diff (em-unix.el) Stefan Kangas
2023-08-13 13:33   ` Eli Zaretskii
2023-08-13 16:49     ` Stefan Kangas
2023-08-13 17:32       ` Jim Porter
2023-08-13 17:54         ` Eli Zaretskii
2023-08-14  7:26           ` Michael Albinus
2023-08-14  9:07             ` Stefan Kangas
2023-08-18  4:33               ` Amin Bandali
2023-08-19 10:54                 ` Stefan Kangas
2023-08-14 12:04             ` Eli Zaretskii
2023-08-15  3:02               ` Jim Porter

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=00c46fb4ab8972714de3d338acbd5040@unbit.co.uk \
    --to=emacs@unbit.co.uk \
    --cc=65245@debbugs.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 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).