unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Kim <habamax@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65049@debbugs.gnu.org
Subject: bug#65049: Minor update to the repro steps
Date: Fri, 4 Aug 2023 21:24:03 +1000	[thread overview]
Message-ID: <CAHFeNPvW=Hgy7QWQSooqvdkf0U22McrNOuh3=YLDKv3YQjxk-A@mail.gmail.com> (raw)
In-Reply-To: <83y1iruky1.fsf@gnu.org>

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

On Fri, Aug 4, 2023 at 9:05 PM Eli Zaretskii <eliz@gnu.org> wrote:

>  I cannot reproduce the problem.  I get the expected behavior: the
>  changes are committed.  Are you sure your recipe is complete?  Do you
>  have any Git customizations, either in that repository or in your
>  system-wide ~/.gitconfig etc.?

I don't have any Git customization in that repo (I tried in several
different repos).
System-wide ~/.gitconfig is:

[user]
name = Maxim Kim
email = habamax@gmail.com
[core]
autocrlf = input
quotepath = off
[credential]
helper = libsecret
[commit]
verbose = true
[pull]
rebase = true
[github]
user = habamax

>  If you have no customizations, please tell more about the recipe, in
>  particular please describe exactly what you see at every step of the
>  recipe.  For example, after "C-x v D" I see the diffs of the single
>  file that is modified in the repository -- is that what you see as
>  well?

Yes I can see diffs of a single or multiple files (in the recipe I had a
single
file with a single diff).

Basically
> 0. ./runemacs.exe -Q
default emacs is opened

> 1. navigate to a dirty git repo
> 2. C-x v D
I can see a single file with a single diff

> 3. Press C-x v v

*vc-log* and *vc-log-files* windows are opened

> 4. Add commit message
add Summary only

> 5. Press C-c C-c

Get the error described in initial message.

Once I am back to my windows laptop, will record a anigif and attach to
mail.

>  FTR: I have the HOME environment variable defined on my Windows system
>  that points to my home directory -- maybe the problem is somehow
>  related to what Emacs considers HOME on Windows when there's no such
>  variable defined? does the directory ../AppData/Local/Temp/ actually
>  exist on your system (and why does Emacs use a relative file name for
>  it, anyway)?

I have also defined HOME as C:/Users/maxim.kim (and it worked for 28.2). I
should probably install 28.2 again and check if it still works.

I am not sure if ../AppData/Local/Temp/ exists as I didn't check what is
default-directory at that moment. But C:/Users/maxim.kim/AppData/Local/Temp/
exists and I've seen other temp files there that looked like emacs+git
related,
smth with MSG in name.

I am not sure why Emacs use relative file name here to be honest.

>  If nothing else gives a clue, please step in Edebug through the
>  relevant code and tell which commands fail, and why (show the values
>  of the relevant variables).

Will check how to use Edebug, thank you!

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

  reply	other threads:[~2023-08-04 11:24 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04  7:50 bug#65049: 29.1; vc-do-command fails in windows emacs 29.1 Maxim Kim
2023-08-04  8:02 ` bug#65049: Minor update to the repro steps Maxim Kim
2023-08-04 11:05   ` Eli Zaretskii
2023-08-04 11:24     ` Maxim Kim [this message]
2023-08-04 17:56     ` Juri Linkov
2023-08-06 23:04       ` Maxim Kim
2023-08-07  1:09     ` Maxim Kim
2023-08-07 16:24       ` Eli Zaretskii
2023-08-07 23:17         ` Maxim Kim
2023-08-20 16:49         ` Juri Linkov
2023-08-20 18:25           ` Eli Zaretskii
2023-08-21  6:53             ` Juri Linkov
2023-08-21 11:00               ` Eli Zaretskii
2023-08-21 11:39                 ` Maxim Kim
2023-08-21 12:18                   ` Eli Zaretskii
2023-08-21 23:10             ` Maxim Kim
2023-08-22 12:52               ` Eli Zaretskii
2023-08-22 13:12                 ` Maxim Kim
2023-08-22 13:17                   ` Eli Zaretskii
2023-08-22 23:43                     ` Maxim Kim
2023-08-23  4:28                     ` Maxim Kim
2023-08-23 16:21                       ` Eli Zaretskii
2023-08-23 17:42                         ` Juri Linkov
2023-08-23 18:43                           ` Eli Zaretskii
2023-08-23 20:13                         ` Dmitry Gutov
2023-08-24  4:54                           ` Eli Zaretskii
2023-08-24 21:06                             ` Dmitry Gutov
2023-08-24 21:35                               ` Dmitry Gutov
2023-08-24 21:44                                 ` Dmitry Gutov
2023-08-25  6:18                                   ` Eli Zaretskii
2023-08-26  0:45                                     ` Dmitry Gutov
2023-08-26  8:50                                       ` Eli Zaretskii
2023-08-27  1:14                                         ` Dmitry Gutov
2023-08-27  5:36                                           ` Eli Zaretskii
2023-08-27 22:32                                             ` Dmitry Gutov
2023-08-28 12:12                                               ` Eli Zaretskii
2023-08-28 13:45                                                 ` Dmitry Gutov
2023-08-28 16:12                                                   ` Eli Zaretskii
2023-08-28 16:51                                                     ` Dmitry Gutov
2023-08-28 16:57                                                       ` Eli Zaretskii
2023-08-28 17:39                                                         ` Dmitry Gutov
2023-08-28 18:26                                                           ` Eli Zaretskii
2023-08-31  2:07                                                             ` Richard Stallman
2023-08-31  2:14                                                               ` Dmitry Gutov
2023-08-31  6:00                                                                 ` Eli Zaretskii
2023-08-23 23:46                         ` Maxim Kim

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='CAHFeNPvW=Hgy7QWQSooqvdkf0U22McrNOuh3=YLDKv3YQjxk-A@mail.gmail.com' \
    --to=habamax@gmail.com \
    --cc=65049@debbugs.gnu.org \
    --cc=eliz@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).