unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Alfred M. Szmidt" <ams@gnu.org>
To: Campbell Barton <ideasman42@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Thoughts on support for vc-diff unsaved buffer contents?
Date: Fri, 22 Nov 2024 01:05:08 -0500	[thread overview]
Message-ID: <E1tEMmy-0002Oe-7k@fencepost.gnu.org> (raw)
In-Reply-To: <68c0ce3e-8316-43db-8f3c-ead0ad028326@gmail.com> (message from Campbell Barton on Fri, 22 Nov 2024 09:02:30 +1100)

   Hi, recently I've run into a situation where it's necessary to calculate 
   modified line ranges without first saving the buffer (where "modified" 
   is determined by a version control diff).

   I'm curious if this is something that might be supported - or, is 
   already supported (although I'm fairly sure it's not).

Maybe diff-buffer-with-file?

   The use case is for auto-formatters only to format modified lines.

   This particular case is for clang-format.el although the same 
   functionality could useful for other formatters too.

   clang-format.el can be configured to format on save,
   so when saving: clang-format.el calculates the lines that differ from 
   the working copy them formats them before saving.

   Currently it's necessary for clang-format.el to call git & diff 
   directly, which makes the functionality limited to git. I was hoping 
   this could be supported in a generic way that uses generic `vc` API's.



  parent reply	other threads:[~2024-11-22  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 22:02 Thoughts on support for vc-diff unsaved buffer contents? Campbell Barton
2024-11-22  0:04 ` James Thomas
2024-11-22  6:05 ` Alfred M. Szmidt [this message]
2024-11-22  7:44 ` Juri Linkov
2024-11-22  9:05   ` Campbell Barton

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=E1tEMmy-0002Oe-7k@fencepost.gnu.org \
    --to=ams@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ideasman42@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.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).