From: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] questions about merlin, vim and the Locate command
Date: Wed, 08 Oct 2014 15:21:40 +0100 [thread overview]
Message-ID: <54354874.5090109@gmail.com> (raw)
Hi,
I have decided to check out Merlin
and configure it with vim editor.
There are two things I failed to figure out and I would be grateful for help.
(1)
When
- I use the "Locate" command
- and the corresponding definition is in the same ML-file
then the cursors jumps to the definition.
Is backtracking supported?
E.g., if you make 10 jumps forward, is it possible to gradually return where you started?
(something similar to the "tag stack" maintained "ctags" / "otags")
(2)
When the corresponding definition is in a different ML-file
then the current window is split into two windows
(one for the original position
one with the requested definition)
Is there a way to prevent this window splitting?
That is, an appropriate buffer at appropriate position would be displayed in the current window?
next reply other threads:[~2014-10-08 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 14:21 Matej Kosik [this message]
2014-10-08 14:27 ` ygrek
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=54354874.5090109@gmail.com \
--to=5764c029b688c1c0d24a2e97cd764f@gmail.com \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).