Hi,
Thanks for the info Bram.
I changed my terminal to send CSI sequence [27;3;121~ for M-y and a vim
mapping for now works :-)
It was related to altSendsEsc logic about what the terminal should send for
these keys.
thx again for all things vim,
-m
On Wednesday, April 7, 2021 at 1:01:30 PM
Indeed. Some plugins are causing the problem. But I also have any files in
~/.vim. How to easily figure out which one causes the problem?
On Tuesday, April 13, 2021 at 5:20:10 PM UTC-5 rwmit...@gmail.com wrote:
> I think there (or at least in my case) is some plugin causing the issue.
> I
I think there (or at least in my case) is some plugin causing the issue.
I didn't even have to change terminals, just 'j' to the bottom of the first
diff file and the screen went blank.
reran again using: vimdiff -u NONE -U NONE and it worked as expected.
I have nearly 50 plugins, so my
Does the vimdiff content reappear if you hit Ctrl-L (on a Mac it might
or might not be Cmd-L, I'm not sure) in Vim? If it does, then there is
a screen refresh missing somewhere.
Best regards,
Tony.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply
On 2021-04-13, Peng Yu wrote:
>
> I don't understand what you mean by "switch to another terminal".
>
>
> On macOS, I use iTerm2 to run vimdiff <(seq 3) <(seq 4). Then open a new tab
> in
> iTerm2. Then go back to the original tab. Then the content in vimdiff
> disappears.
Thanks for the
Thanks very much. Yes, that'll do the trick. Not all pages, but just any
individual one I happen to be reading, so I can edit and take notes on it.
Thanks very much, really appreciate it.
Julius
On Tue, Apr 13, 2021, 15:32 Christian Brabandt wrote:
>
> On Di, 13 Apr 2021, Julius Hamilton
Gary Johnson wrote:
> On 2021-04-13, Peng Yu wrote:
> > When I call `vimdiff <(seq 3) <(seq 4)`, then switch to another terminal
> > then
> > switch back, the content in vim disappear. How to make the content
> > persistent?
>
> I run vimdiff with process substitution like that all the time
> I don't understand what you mean by "switch to another terminal".
>
On macOS, I use iTerm2 to run vimdiff <(seq 3) <(seq 4). Then open a new
tab in iTerm2. Then go back to the original tab. Then the content in
vimdiff disappears.
--
--
You received this message from the "vim_use"
Christian wrote:
> On Di, 13 Apr 2021, Julius Hamilton wrote:
>
> > Someone showed me ":hardcopy" and ":TOhtml". ":hardcopy" for me returns
> > "Failed
> > to print postscript file". "TOhtml" opens a new window of HTML, but I don't
> > know how to output it to a file. Would anyone here know
On Di, 13 Apr 2021, 'Ottavio Caruso' via vim_use wrote:
> I wonder if you all could be so kind and forgive my hijack attempt and
> ask you if this is also possible with good ol' fashioned vi/nvi?
>
> I would like to dump the output of :viu and :exu to to a file. I've
> looked into these
On 2021-04-13, Peng Yu wrote:
> When I call `vimdiff <(seq 3) <(seq 4)`, then switch to another terminal then
> switch back, the content in vim disappear. How to make the content persistent?
I run vimdiff with process substitution like that all the time
without losing anything. The outputs of
On Tue, 13 Apr 2021 at 08:51, Christian Brabandt wrote:
>
>
> On Mo, 12 Apr 2021, Julius Hamilton wrote:
>
> > Is there any way to output the content of the Vim help pages to a text
> > file, with some sort of dump or output command?
>
> The help pages are text files, you don't need to dump
Hi Peng Yu,
those pipes are not seek-able files and may not be read again — maybe this is.
Also, this problem sounds very very similar the your previous one.
Best Regards,
CM
Peng Yu schrieb am 13.04.2021 16:39:56:
> When I call `vimdiff <(seq 3) <(seq 4)`, then switch to another terminal
>
When I call `vimdiff <(seq 3) <(seq 4)`, then switch to another terminal
then switch back, the content in vim disappear. How to make the content
persistent? Thanks.
$ vimdiff --version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Apr 1 2021 08:37:51)
macOS version - x86_64
Included patches:
Yes. It works. Thanks.
On Tuesday, April 13, 2021 at 6:48:59 AM UTC-5 rwmit...@gmail.com wrote:
> What does that do that:
>
> seq 10 | vim -
>
> doesn't?
>
> On Tuesday, April 13, 2021 at 12:22:25 AM UTC-4 Peng Yu wrote:
>
>> Hi,
>>
>> When I use the following command to open something from
On Di, 13 Apr 2021, Julius Hamilton wrote:
> Someone showed me ":hardcopy" and ":TOhtml". ":hardcopy" for me returns
> "Failed
> to print postscript file". "TOhtml" opens a new window of HTML, but I don't
> know how to output it to a file. Would anyone here know how to do that?
So you want
Someone showed me ":hardcopy" and ":TOhtml". ":hardcopy" for me returns
"Failed to print postscript file". "TOhtml" opens a new window of HTML, but
I don't know how to output it to a file. Would anyone here know how to do
that?
Thanks very much,
Julius
On Tue, Apr 13, 2021, 14:30 Julius Hamilton
Thanks very much.
Sorry, I don't fully understand how to use that. That seems to be a long
document about many different options. Is there listed somewhere in there
the option to output a Vim help page to an external file?
For example, the Unix info reader allows outputting of an info page with
On Mo, 12 Apr 2021, Peng Yu wrote:
> Hi,
>
> When I use the following command to open something from stdin, it will
> reset the content on the screen when I switch between terminals. Is
> there a way to keep the content persistent while I switch between
> terminals? Thanks.
>
> seq 10 | { vim
What does that do that:
seq 10 | vim -
doesn't?
On Tuesday, April 13, 2021 at 12:22:25 AM UTC-4 Peng Yu wrote:
> Hi,
>
> When I use the following command to open something from stdin, it will
> reset the content on the screen when I switch between terminals. Is
> there a way to keep the
On Tuesday, April 13, 2021 at 12:22:25 AM UTC-4 Peng Yu wrote:
> Hi,
>
> When I use the following command to open something from stdin, it will
> reset the content on the screen when I switch between terminals. Is
> there a way to keep the content persistent while I switch between
>
On Mo, 12 Apr 2021, Julius Hamilton wrote:
> Is there any way to output the content of the Vim help pages to a text file,
> with some sort of dump or output command?
The help pages are text files, you don't need to dump them, you can
:e $VIMRUNTIME/doc/options.txt
to read the options help
Hey,
Is there any way to output the content of the Vim help pages to a text
file, with some sort of dump or output command?
Thanks very much,
Julius Hamilton
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For
23 matches
Mail list logo
