Tuesday, December 28, 2010

Re: How to recall what bookmarks I defined?

I am no programming expert, I use Vim mainly for writing, but you
sound as if you are interested in something more semi-permanent than a
mere mark. Have you ever tried ctags?

http://ctags.sourceforge.net/

This could enable you to keep all the "marks" you want and also call
them by any name you please.

Just a suggestions.

RD

On Dec 28, 11:10 am, Steven Woody <narkewo...@gmail.com> wrote:
> On 28 December 2010 04:33, Tom Link <micat...@gmail.com> wrote:
>
>
>
> >> 1. It's hard to recall what marks I defined -- local marks and global
> >> marks.
>
> > Are you looking for the :marks command?
>
> > There are a few plugins that display marks as signs on the left-hand
> > side. One of them is (my own) quickfixsigns. But there are others on
> > vim.org that may better fit your needs. It seems that over on vim.org
> > there are at least two plugins called showmarks that achieve something
> > similar. I personally also find that plugins like wokmarks and (my
> > own :-) tmarks make it easier to deal with marks. YMMV and, again,
> > maybe other plugins suit your editing habits better.
>
> > HTH
> > Tom
>
> Thanks Tom!  I found quickfixsigns does not correct refresh its status
> bar, showmarks does not work at all, and workmarks does not do global
> marks.  So the only one left is your tmarks.  The 'TMarks' list better
> information than the build-in 'marks' command.  Thanks for your work.
> So the issue remained open to me is that how to prevent me from
> accidently overwrite an previously defined mark.  If one of above
> bookmark visualization tools works, it would be resolved.
>
> Thanks.
>
> -
> narke
>
> --
> Life is the only flaw in an otherwise perfect nonexistence
>     -- Schopenhauer
>
> narke
> public key athttp://subkeys.pgp.net:11371(narkewo...@gmail.com)

--
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

No comments:

Post a Comment