From: Jambunathan K <kjambunathan@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 9503@debbugs.gnu.org
Subject: bug#9503: 24.0.50; (vc-git): After applying a stash, refresh of *vc-dir* is a must
Date: Thu, 15 Sep 2011 10:21:20 +0530 [thread overview]
Message-ID: <81vcsuqugn.fsf@gmail.com> (raw)
In-Reply-To: <CAAeL0SQeWD=A=+vhhXvJxY1OKkJ=_NvRv9GwdtcgE01LfjkDKA@mail.gmail.com> (Juanma Barranquero's message of "Wed, 14 Sep 2011 20:49:30 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> On Wed, Sep 14, 2011 at 20:18, Jambunathan K <kjambunathan@gmail.com> wrote:
>
>> I would prefer to have some sort of visual feedback that confirms that
>> the application of stash has succeeded. Otherwise I just keep staring at
>> the screen hoping something would happen.
>
> Agreed.
>
>> Do you think a prefix arg or a customization variable is in order?
>
> A prefix arg, for the case that you *don't* want the autoupdate,
> perhaps. Your case is surely more common that the one where the user
> wants to apply several stashes at once. As for the variable, it
> wouldn't be useful if you usually apply one stash, and in a few cases
> you want to apply several.
Considering that stashes cannot be applied on a dirty tree, refreshing
the *vc-dir* would invariably follow (if one is committing from within
Emacs)
There seem to be only two options after a clean application of stash
1. Continue modify the working tree.
2. Commit the stash.
May be the prefix arg could be used to mean (2) above? I am more likely
to do (1) than (2).
Now I believe there is a strong case for refreshing *vc-dir*.
>> You can close this bug if you think it is too frivolous.
>
> No, not at all. I just wondered about the other use case, because it
> isn't uncommon for me.
> Juanma
next prev parent reply other threads:[~2011-09-15 4:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 10:20 bug#9503: 24.0.50; (vc-git): After applying a stash, refresh of *vc-dir* is a must Jambunathan K
2011-09-14 11:09 ` Juanma Barranquero
2011-09-14 18:18 ` Jambunathan K
2011-09-14 18:45 ` Stefan Monnier
2011-09-14 18:49 ` Juanma Barranquero
2011-09-15 4:51 ` Jambunathan K [this message]
2011-09-15 4:35 ` Jambunathan K
2011-09-15 7:34 ` Andreas Schwab
2011-09-15 8:07 ` Jambunathan K
2013-11-15 5:08 ` Jambunathan K
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=81vcsuqugn.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=9503@debbugs.gnu.org \
--cc=lekktu@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).