I am trying to write a .vimrc for a few Solaris 10 vm's in ESXi server.
After forcing the terminal to various different attempts I can sort of
get what I want from the vi client's console but as I scroll down, once
I reach the end of the screen only the last line updates or other odd
things
With the lack of details, it's really hard to say, but - that sounds
like what would happen if $LINES or $COLUMNS were set incorrectly and
vim wasn't able to ask the terminal what the correct number of lines
and columns are.
Matt,
Thanks for taking the time to help and I apologize for the lack of
Well, that is flat out wrong on Solaris. Solaris definitely doesn't
provide any terminals that would qualify as $TERM == 'linux'
I know, but it was one that sort of worked the least wrong :)
Probably not related to your problem, but 'set nocompatible' should be
the first line in your vimrc.
Well, check the values that $LINES and $COLUMNS have in a shell, and
make sure that they match the actual number of lines and columns that
the terminal has.
Ok, its 80x25 which didn’t make a difference with it set.
You didn't answer the question about other full-screen curses apps.
Ok, I had
What's the terminal emulator you're running?
What do you launch to bring it up? What's the name of the
application?
Guide me through this one? When working at the console, I understand
there isn't an emulator used? Maybe I am confused. When ssh'ing in from
a win or linux box, I use putty or
Its set to VT100 at boot:
Matt,
This finally led me in the right direction. The correct terminal type
that works perfectly was sun-color. What a learning expedition :)
Thanks for everything!
jlc
--~--~-~--~~~---~--~~
You received this message from the vim_use
For as long as I can remember, when gvim detects a file has changed and prompts
to reload, the file is reloaded with some quantity of the initial contents
replaced with a the letter "g" and a back tick? A google search didn't reveal
anything.
Anyone know of a solution?
--
--
You received
On Friday, September 8, 2017 at 10:59:43 AM UTC-6, Ben Fritz wrote:
> I've certainly never seen that before! What version of Vim are you using?
> Does it happen every time?
>
> Have you tried reproducing without any plugins or customizations? This sounds
> like it's probably a plugin issue to
On Friday, September 8, 2017 at 11:32:30 AM UTC-6, Christian Brabandt wrote:
> Is this really there or does a :redraw fix it? If the latter, I would
> guess it is a graphics driver issue.
>
> BTW: I have never encountered such an issue with gvim
>
>
> Best,
> Christian
I will try that next
On Friday, September 8, 2017 at 2:12:28 PM UTC-6, Christian Brabandt wrote:
> Looks like a bom. Can you check the hex version of the file? What is
> your fencs setting, does it work, if you add ucs-bom to it?
>
> Best,
> Christian
The current setting is ucs-bom. The odd thing is it doesn't
I have a utf-16-le based file with a bom which I can view on a linux host with
vi without issue:
# file utf16.txt
utf16.txt: Little-endian UTF-16 Unicode text, with CRLF line terminators
# od -t x1 -N 2 utf16.txt
000 ff fe
002
It opens and appears as expected with vi at the console
On Saturday, September 9, 2017 at 12:16:27 PM UTC-6, Tony Mechelynck wrote:
> In your Windows gvim, at the point where you would be reading your
> problematic file, do instead
>
> :verbose set enc?
>
> If the answer is anything other than utf-8, then you cannot display
> the file in gvim
On Sunday, September 10, 2017 at 12:28:12 AM UTC-6, Tony Mechelynck wrote:
> Despite its name, ++enc sets 'fileencoding' (telling Vim which charset
> is used _on disk_ for that file), not 'encoding' (the charset used for
> the data _in Vim memory_); the latter, if you don't change it, is
> still
On Friday, September 8, 2017 at 1:46:27 PM UTC-6, Joseph L. Casale wrote:
> I will try that next time, unfortunately I cannot manually repro it so I will
> post back once it occurs.
And of course just after I post, it occurs. The attached picture illustrates
the issue in a form I have no
I have a use case where the optimal tool for my need is gvim as I don't have
access to anything more suitable in the context. I am trying to invoke gvim as
a process to perform a replacement (no shell or batch based invocation).
The arguments I am passing (which are simply string joined with a
On Friday, November 3, 2017 at 1:49:18 PM UTC-6, Ben Fritz wrote:
> > "-c",
> > "\"%s/.*foo.*/bar/g | w\"",
> Why gvim and not console vim? I don't know if it is the cause, but if you
> must use gvim then on Linux and similar systems you need to also pass the
> "-f" argument if you
On Friday, June 29, 2018 at 10:55:25 AM UTC-6, Gary Johnson wrote:
> There's also sdiff:
>
> sdiff file1 file2 | less
>
> or
>
> sdiff file1 file2 | vim -
That worked brilliantly!
Thanks.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply
On Wednesday, April 4, 2018 at 2:40:54 PM UTC-6, Bram Moolenaar wrote:
> > SIDs such as S-1-22-1-990 and S-1-22-2-988 respectively.
> >
> > Editing a local file does not trigger the behavior.
> >
> > If I can provide any additional details, just let me know.
>
> Hmm, is this really a problem
Seems the permissions are wrong and mapped to unknown sids in this release. I
am not even sure what repo this should filed against?
--
--
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
On Tuesday, April 3, 2018 at 4:50:40 AM UTC-6, Bram Moolenaar wrote:
> You will have to give more information, I have no idea what you are
> talking about.
Hi Bram,
I have narrowed this down a bit, when editing a file on a Samba share
mapped to a Windows drive such as s:\foo, the resulting
Does a means or plugin exist to perform a diff between two tabs/files that
compares entire lines?
Thanks.
--
--
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
On Friday, June 29, 2018 at 8:57:45 AM UTC-6, Gary Johnson wrote:
> I _think_ I understand what you want, but I don't know of a way to
> make Vim's internal comparison algorithm do that.
>
> Either of these two Linux commands will generate an output of only
> the lines common to file1 and file2,
On Thursday, June 28, 2018 at 7:46:51 PM UTC-6, Tony Mechelynck wrote:
> No plugin required, provided that you have a Vim compiled with +diff
> and that the diff utility is installed and can be found on your $PATH.
>
> See ":help diff.txt"
Hi Tony,
Specifically, I need to match lines completely
23 matches
Mail list logo
