From: Richard Stallman <rms@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 16214@debbugs.gnu.org, larsi@gnus.org,
tkk@misasa.okayama-u.ac.jp, roland@hack.frob.com,
josh@foxtail.org
Subject: bug#16214: Consistency in dired-, occur-, and grep-mode
Date: Mon, 14 Feb 2022 23:30:01 -0500 [thread overview]
Message-ID: <E1nJpTV-0007RX-GO@fencepost.gnu.org> (raw)
In-Reply-To: <87k0dyx7ms.fsf@gmx.de> (message from Michael Albinus on Mon, 14 Feb 2022 07:52:11 +0100)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > I it is the former, I am surprised that you create a new file every
> > day. When I was working on software, I would make changes every day,
> > but new files were rare. How is it that you have such frequent
> > occasions to put a new file into version control? I'd like to
> > understand what leads to this.
> 'v' in vc-dired means 'vc-next-action'. It does whatever vc command is
> appropriate at the given context. In my use case, I apply it in order to
> commit a file or fileset. Every single day.
Boy am I spaced! I knew that command, but didn't recall it. All I
was thinking about was the previous messages which talked about v as
registering a file.
Sorry for the confusion.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-02-15 4:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 13:40 bug#16214: Consistency in dired-, occur-, and grep-mode Tak Kunihiro
2013-12-21 19:23 ` Drew Adams
2013-12-21 20:15 ` Josh
2013-12-21 21:30 ` Juri Linkov
2013-12-22 11:48 ` Tak Kunihiro
2013-12-22 21:44 ` Juri Linkov
2013-12-23 11:34 ` Tak Kunihiro
2013-12-23 21:52 ` Juri Linkov
2013-12-24 23:15 ` Tak Kunihiro
2013-12-25 20:57 ` Juri Linkov
2013-12-28 9:57 ` Tak Kunihiro
2022-02-10 8:27 ` Lars Ingebrigtsen
2022-02-10 9:26 ` Tak Kunihiro
2022-02-10 11:37 ` Lars Ingebrigtsen
2022-02-11 5:54 ` Tak Kunihiro
2022-02-12 3:57 ` Richard Stallman
2022-02-12 8:16 ` Michael Albinus
2022-02-14 4:13 ` Richard Stallman
2022-02-14 6:52 ` Michael Albinus
2022-02-15 4:30 ` Richard Stallman [this message]
2022-02-12 19:12 ` Howard Melman
2022-02-12 20:43 ` Howard Melman
2022-02-14 4:14 ` Richard Stallman
2022-02-17 16:28 ` Howard Melman
2022-02-17 17:12 ` bug#16214: [External] : " Drew Adams
2022-02-20 1:43 ` Tak Kunihiro
2022-02-20 18:17 ` Howard Melman
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=E1nJpTV-0007RX-GO@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=16214@debbugs.gnu.org \
--cc=josh@foxtail.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=roland@hack.frob.com \
--cc=tkk@misasa.okayama-u.ac.jp \
/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).