On Thu, Nov 21, 2013 at 02:04:55PM -0800, Ari wrote:
> When I open a pre-existing file with gVim 7.4 (on Windows 8), gVim
> complains about modeline issues, i.e. complaining that there are
> special characters at the end of the file like: ^J or ^M. Does anyone
> know how to resolve this? I added "set nocompatible" to the _vimrc
> (.vimrc) file.
> Moreover, the formatting of files are not maintained. For example,
> when I open a file in Emacs the content includes return, tab, etc.
> characters; however, when I open the same file in gVim, the content is
> displayed in a straight line. Example follows. Does anyone what is the
> cause of this issue and how to resolve it?
> Emacs:
> {
> "name": Ari,
> "tools": ["Emacs", "Vi", "Vim"],
> ...
> }
> gVim:
> { "name": Ari, "tools": ["Emacs", "Vi", "Vim"], ... }
I have a logfile created by procmail which, when I open it, it barks
about improper values in my modeline, when in fact there is no actual
modeline, but many lines containing "vim:"
My first attempt to open it politely I used
gvim + -c 'set nomodeline' procmail.log
which still gave the error. Then in a recent thread I was reminded that
the start option "--cmd" does stuff sooner than "-c", so
gvim + --cmd 'set nomodeline' procmail.log
opens the file with no error about invalid modeline.
(The "+" sends me to the end of the file which is where my interest
lies.)
Then I put it all in a bash script (.bat file for you) so I wouldn't
have to type all that every time I want to see the bottom of that file.
hth,
--
_|_ _ __|_|_ ._ o|
|_(_)(_)|_| ||_)||<
|
--
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Thursday, November 21, 2013
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment