From: James Darnley <james.darnley@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Vim and cursor position
Date: Sun, 14 Feb 2016 22:18:00 -0000 [thread overview]
Message-ID: <56C0FD1C.7070300@gmail.com> (raw)
In-Reply-To: <20160214202433.GA3865@phoenix>
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
On 2016-02-14 21:24, Gary Johnson wrote:
> On 2016-02-14, James Darnley wrote:
>> To the maintainer, Yaakov, or anyone else who knows:
>>
>> Have the compilation options of Vim changed recently? Is there some
>> other recent change that would cause the behaviour described below?
>>
>> Vim now appears to be remembering the last position of the cursor when
>> you open files. I notice it most when running 'git commit', the cursor
>> never starts on the first line but would appear to be where ever I ended
>> the previous message.
>>
>> I find this jolly annoying.
>>
>> I would appreciate any insights people can offer.
>
> Recent releases of the Cygwin Vim package (starting with 7.4.1179-1,
> 2016-01-29) have included Red Hat's or Fedora's /etc/vimrc, which is
> loaded first when starting Vim. That file contains a BufReadPost
> autocommand to do what you observe.
>
> I don't like it, either, so I have this in my ~/.vimrc:
>
> " Remove the (annoying) /etc/vimrc autocommand that positions
> " the cursor " to the location it last had when the file was
> " closed.
> "
> if exists("#fedora#BufRead#*")
> au! fedora BufRead *
> endif
> if exists("#redhat#BufRead#*")
> au! redhat BufRead *
> endif
>
> For Cygwin, you need only one of those, but I'm at home, my Cygwin
> installation is at work, and I don't remember whether Cygwin uses
> the Fedora or the Red Hat version of /etc/vimrc.
>
> You may want to take a look at /etc/vimrc and see if it makes any
> other settings you find undesirable and undo them in your ~/.vimrc
> as well.
>
> Regards,
> Gary
Thank you very much. For everyone's information: /etc/vimrc appears to
group things under "fedora".
P.S. Sorry about the double mail Gary.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 603 bytes --]
prev parent reply other threads:[~2016-02-14 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 16:34 James Darnley
2016-02-14 20:23 ` Gary Johnson
2016-02-14 21:35 ` Andrey Repin
2016-02-14 22:18 ` James Darnley [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56C0FD1C.7070300@gmail.com \
--to=james.darnley@gmail.com \
--cc=cygwin@cygwin.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.
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).