unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: "C.J.S. Hayward" <cjsh@cjshayward.com>
Cc: 70562@debbugs.gnu.org
Subject: bug#70562: Trouble using Vim under Emacs's ansi-term
Date: Thu, 25 Apr 2024 06:59:53 +0000	[thread overview]
Message-ID: <877cgmorkm.fsf@posteo.net> (raw)
In-Reply-To: <WdadJvFzdWIPud99damsJTiRXHgFw1xNZiXJUgCuAcgOGk8G8KjtHSXAfroeHoXjw8CC0Nlz2-MPi7Dhn_UnL8r4B01ECMVOQ0Ipi8lGWJ0=@cjshayward.com> (C. J. S. Hayward's message of "Wed, 24 Apr 2024 17:42:41 +0000")

"C.J.S. Hayward" <cjsh@cjshayward.com> writes:

> I have Emacs 21 as installed from Linux Mint Victoria.

Do I understand correctly, that you are using Emacs 21, released
somewhere between 2001 and 2005?

> I am a long-time Vim user interested in a proportional font terminal,
> such as is mostly provided by Emacs Evil mode or local or (ssh) remote
> Vim, but I have experienced consistent issues using vim under Emacs's
> ansi-term.
>
> I haven't been able to pin down that if you edit a particular document
> and attempt a particular set of keystrokes, issues arise. However, I
> have had issues with Emacs thinking it is one line higher or lower
> than it really is, so that commenting out a line of JavaScript
> comments out a different line from what the user intended (and what it
> appears), and random freezing.
>
> I believe that if you have a volunteer who is comfortable using Vim,
> and ask said user to use Vim under Emacs's ansi-term for half an hour
> (I have not been able to discern different behavior between local Vim
> processes and those ssh'ed into a Linux server), the odd behaviors I
> have experienced will be reproduced. Based on my own experience, I
> believe some inappropriate behavior will probably be noticeable in 2-5
> minutes, but I mention half an hour as adding slop.

I am comfortable enough with vi(m) and I tried out some non-trivial text
manipulation but couldn't notice anything wrong.  If you are actually
using Emacs 21, then it might be that in the ~20 years since its release
the bugs causing the issues you have been having have been resolved?  I
would also recommend trying out the ELPA package "eat" as an alternative
terminal emulator, but that would also require a newer version of Emacs.

>
> Thanks,
>
>
> Unworthy Br. Christos Hayward (really, thou / thee / thy / thine), novice at St. Demetrios Orthodox Monastery.
>
> Most recent posting: A Note to Single Evangelical Women
>
> Websites:
>
> C.J.S. Hayward: Official Author Site (Bookshelf)Official Substack
> Orthodox Church Fathers
> The Powered Access Bible
> Scrolls of Wonder
>
>
>
>

-- 
	Philip Kaludercic on peregrine





      reply	other threads:[~2024-04-25  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 17:42 bug#70562: Trouble using Vim under Emacs's ansi-term C.J.S. Hayward
2024-04-25  6:59 ` Philip Kaludercic [this message]

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=877cgmorkm.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=70562@debbugs.gnu.org \
    --cc=cjsh@cjshayward.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).