Christian,
Thanks for the reply! Unfortunately I don't have gvim installed (I could never get the hang of using it). I tried in iTerm, which had a similar issue as Alacritty (lines slightly shorter, but still lots of visual space between the lines of the E325 ATTENTION message). But Terminal.app didn't have the same problem. So I thought,"Aha! It's different termcaps causing the issue!" In Terminal.app TERM is defaulting to xterm-256color, whereas in iTerm it was set to screen-256color, and in Alacritty I use tmux heavily so it was set to tmux-256color.
Unless you can think of a better way to solve this, I can just set up an alias for vim='TERM=xterm-256color vim' and that will be a sufficient workaround for my purposes. When I executed `TERM=xterm-256color vim` manually it fixed the problem.
On Sat, Sep 30, 2023 at 5:09 PM Christian Brabandt <cblists@256bit.org> wrote:
On Fr, 29 Sep 2023, 'Trey Blancher' via vim_use wrote:
> I'm using vim 9.0.1850 on macOS Ventura 13.6, installed via Homebrew. I
> have a problem with the E325 ATTENTION message, informing me of an existing
> swap file. It appears that every line in the message is inordinately long,
> such that most of the message scrolls off the top of my terminal emulator
> window (and I can't scroll up to see it since I'm using vim in a tmux
> session/window/pane in Alacritty). This looks like a formatting or a text
> wrapping*s* problem.
>
> Here's a link to what I've copied out to the visible window, to try and
> demonstrate what I'm running into: https://paste.rs/TUl2R (it doesn't
> appear I can attach files to this Google Groups message). Here's a
> screenshot from my vertical rotated monitor: [image: Screenshot 2023-09-29
> at 15.22.48.png]
>
> This has been going on for quite some time, I don't know exactly when it
> started. Is there any way to fix this?
This is surprising and I have never seen this issue. Does it only happen
in Alacritty? Always? Can you check in different terminal emulators and
also in the GUI? What once it shows up, you abort vim, and restart using
`vim --clean` and then open the exact same file (so the E325 should
trigger again)?
Thanks,
Christian
--
Look at it this way: Your daughter just named the fresh turkey you brought
home "Cuddles", so you're going out to buy a canned ham. And you're still
drinking ordinary scotch?
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to a topic in the Google Groups "vim_use" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_use/qj4f8eYkQ5U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ZRiOdoDKSjKXWmP5%40256bit.org.
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CABzFwhU1MkE7Lro2HNfXuVKVGRpmf7dry5AT3phyhW3yyOrGWw%40mail.gmail.com.
No comments:
Post a Comment