From: Urban Engberg <urban@engbergs.dk>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 59232@debbugs.gnu.org
Subject: bug#59232:
Date: Wed, 20 Dec 2023 22:36:24 +0100 [thread overview]
Message-ID: <CALqErGQfsuYpsnbXdYwqhqJkP06g-QFL0qMmZZ2wKZsrhJPNug@mail.gmail.com> (raw)
In-Reply-To: <5bbef471-5914-c370-8ecb-1fe2af815351@gutov.dev>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Wed, 20 Dec 2023 at 19:35, Dmitry Gutov <dmitry@gutov.dev> wrote:
> Maybe the command might fails when run in a non-interactive terminal?
>
> You can try emulating the same circumstances in the shell by doing
> something like this:
>
> echo "" | git blame README | cat
>
> (Of course, by replacing the command in the middle with the SVN command
> that actually runs.)
>
I thought about that too, namely as it does not fail when setting
process-conection-type to t. But no,
echo "" | svn --non-interactive annotate Program.java | cat
works just fine.
I shortened the failing statement down to
(let ((process-connection-type nil))
(start-process
"xxx"
"*Test*"
"svn"
"annotate" "FILE"))
where FILE contains more than 100 lines – that also seems to be
significant, and using --non-interactive is not. But I am still not able to
figure out if it is the svn command itself that crashes, or it has
something to do with the process communication and Emacs. If it's the
first, it should be possible to find a way that this crashes as well when
run from the shell.
--
urban@engbergs.dk, 5679+MHJ Århus
<https://www.google.com/maps?q=9F8G5679%2BMHJ>
[-- Attachment #2: Type: text/html, Size: 2253 bytes --]
next prev parent reply other threads:[~2023-12-20 21:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 0:14 bug#59232: 27.2; vc-annotate on SVN does not process all lines Pierre Rouleau
2022-11-13 2:29 ` Dmitry Gutov
2022-11-13 14:42 ` Pierre Rouleau
2022-11-13 2:30 ` Dmitry Gutov
2022-11-13 14:59 ` Pierre Rouleau
2022-11-13 6:36 ` Eli Zaretskii
2022-11-13 14:51 ` Pierre Rouleau
2022-11-13 15:11 ` Pierre Rouleau
2022-11-13 16:10 ` Andreas Schwab
2022-11-13 16:40 ` Eli Zaretskii
2022-11-13 18:05 ` Pierre Rouleau
2022-11-13 23:54 ` Stephen Berman
2022-11-14 3:48 ` Pierre Rouleau
2022-11-13 8:12 ` Andreas Schwab
2022-11-13 14:55 ` Pierre Rouleau
2023-12-20 12:41 ` bug#59232: Urban Engberg
2023-12-20 15:50 ` bug#59232: Dmitry Gutov
2023-12-20 17:38 ` bug#59232: Urban Engberg
2023-12-20 18:35 ` bug#59232: Dmitry Gutov
2023-12-20 21:36 ` Urban Engberg [this message]
2023-12-20 22:03 ` bug#59232: Dmitry Gutov
2023-12-20 22:50 ` bug#59232: Urban Engberg
2023-12-21 0:12 ` bug#59232: Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALqErGQfsuYpsnbXdYwqhqJkP06g-QFL0qMmZZ2wKZsrhJPNug@mail.gmail.com \
--to=urban@engbergs.dk \
--cc=59232@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.