From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Khoa Vo <vodangkhoa873@gmail.com>, 48399@debbugs.gnu.org
Subject: bug#48399: 27.2; term-mode: After splitting window, newlines are inserted
Date: Mon, 11 Jul 2022 16:57:44 +0200 [thread overview]
Message-ID: <87czebg0if.fsf@gmail.com> (raw)
In-Reply-To: <87o7xvsocm.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 11 Jul 2022 16:42:01 +0200")
>>>>> On Mon, 11 Jul 2022 16:42:01 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Khoa Vo <vodangkhoa873@gmail.com> writes:
>> Note: I have repoduced this bug even without a configuration file.
>>
>> Steps:
>> - Enter term-mode.
>> - Enter term-line-mode.
>> - Type a command one line below the prompt, but don't hit "enter" yet.
>> - Issue command "M-x split-window-right".
>> - You can see the problem: one or more new lines are inserted after the prompt.
>> Pushing the command further down.
Lars> (I'm going through old bug reports that unfortunately weren't resolved
Lars> at the time.)
Lars> I'm not sure I understand the problem. If by "Enter term-mode" you mean
Lars> `M-x term RET RET', then commands like `M-x split-window-right' aren't
Lars> available, so perhaps you mean something else?
Lars> Can you give a step-by-step recipe to reproduce the problem, starting
Lars> from "emacs -Q"?
M-x term
C-c C-j
C-n
ls C-x 3
reproduces for me (you can run any normal Emacs command when youʼre in term-line-mode)
Robert
--
next prev parent reply other threads:[~2022-07-11 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 9:14 bug#48399: 27.2; term-mode: After splitting window, newlines are inserted Khoa Vo
2022-07-11 14:42 ` Lars Ingebrigtsen
2022-07-11 14:57 ` Robert Pluim [this message]
2022-07-11 15:48 ` Michael Heerdegen
2022-07-12 12:28 ` Lars Ingebrigtsen
2022-07-12 13:13 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-12 13:27 ` Michael Heerdegen
2022-07-12 13:48 ` Andreas Schwab
2022-07-12 13:40 ` Eli Zaretskii
2022-07-12 14:14 ` Andreas Schwab
2022-07-12 14:26 ` Andreas Schwab
2022-07-12 22:21 ` Lars Ingebrigtsen
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=87czebg0if.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=48399@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=vodangkhoa873@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).