From: 6o205zd02@sneakemail.com
To: 9fans@9fans.net
Subject: Re: [9fans] Codebase navigation and using tags files in acme
Date: Wed, 18 Aug 2021 20:51:11 -0700 [thread overview]
Message-ID: <848-1629345074-357948@sneakemail.com> (raw)
In-Reply-To: <CAHqDL__Dw7RCWwe34vD7Gn5Y32B+7SsPmD1ZBZOhimTfZNOyFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3003 bytes --]
I had never heard of acme-lsp and LSP (except as a Microsoft internal
thing) until gabi mentioned it earlier in the thread. I'm interesting
in playing with acme-lsp for C++. Which LSP server do you use for C/C++
(I see several listed at https://langserver.org/)?
thanks,
Peter
On 2021-08-18 02:26, Ole-Hjalmar Kristensen
ole.hjalmar.kristensen-at-gmail.com |9fans| wrote:
> On linux, you can run ctags -x and postprocess the file to append the
> line number to the file name instead of having i as a separate field.
> That way, you can locate the symbol in the tags file, and right-click
> on the file:linenumber.
>
> Also, on linux, we have acme-lsp, which in principle works with any
> LSP server. I have tested it with go and C/C++.
>
> On Tue, Aug 17, 2021 at 10:22 PM Ben Hancock <ben@benghancock.com
> <mailto:ben@benghancock.com>> wrote:
>
> Hello 9fans,
>
> I've just recently started using the acme editor and am really
> enjoying
> it, and trying to get the hang of the "acme way" of doing things. One
> bit of functionality that I'm familiar with from other editors is the
> ability to easily look up a function or symbol definition within a
> codebase. In Emacs and vi, this is done by generating tags files
> (etags
> or ctags), which those editors can parse and allow you to easily
> jump to
> a definition of the symbol under the point/cursor.
>
> What's the preferred method or workflow for achieving this in acme? I
> have tried passing a selected symbol to 'g -n' in the window's tag,
> using the Mouse-2 + Mouse-1 chord. That gets me part of the way there
> but isn't effective if the file where the symbol is defined
> happens to
> be in another directory. I feel like I'm missing something.
>
> Many thanks!
>
> - Ben
>
> --
> Ben Hancock
> www.benghancock.com <http://www.benghancock.com>
>
> ------------------------------------------
> 9fans: 9fans
> Permalink:
> https://9fans.topicbox.com/groups/9fans/Tf8ceac12df9da674-M693d75f3d4f4ad66ecaa27e0
> <https://9fans.topicbox.com/groups/9fans/Tf8ceac12df9da674-M693d75f3d4f4ad66ecaa27e0>
> Delivery options:
> https://9fans.topicbox.com/groups/9fans/subscription
> <https://9fans.topicbox.com/groups/9fans/subscription>
>
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/Tf8ceac12df9da674-Mb6807aa0e9520cbbc2e097ad>
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf8ceac12df9da674-M652caba65026de9632210a05
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 4491 bytes --]
next prev parent reply other threads:[~2021-08-19 3:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 20:22 Ben Hancock
2021-08-18 6:52 ` sirjofri
2021-08-18 9:12 ` Richard Miller
2021-08-18 9:17 ` Gabriel Diaz Lopez de la Llave via 9fans
2021-08-18 9:25 ` Rob Pike
2021-08-18 16:01 ` Ben Hancock
2021-08-19 11:44 ` Maurizio Boriani
2021-08-19 11:49 ` Gorka Guardiola
2021-08-19 18:59 ` unobe
2021-08-19 19:00 ` unobe
2021-08-19 20:41 ` Rob Pike
2021-08-18 9:13 ` Nick Owens
2021-08-18 9:26 ` Ole-Hjalmar Kristensen
2021-08-19 3:51 ` 6o205zd02 [this message]
2021-08-19 7:29 ` igor
2021-08-20 10:55 ` Ole-Hjalmar Kristensen
2021-08-20 23:08 ` a
2021-08-20 23:31 ` Steve Simon
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=848-1629345074-357948@sneakemail.com \
--to=6o205zd02@sneakemail.com \
--cc=9fans@9fans.net \
/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).