all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joel Reicher <joel.reicher@gmail.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: Help Gnu Emacs Mailing List <help-gnu-emacs@gnu.org>
Subject: Re: Tagging Fortran variables
Date: Wed, 07 Aug 2024 12:38:54 +1000	[thread overview]
Message-ID: <8634nhawg1.fsf@gmail.com> (raw)
In-Reply-To: <87jzgur4ig.fsf@librehacker.com> (Christopher Howard's message of "Mon, 05 Aug 2024 14:25:43 -0800")

Christopher Howard <christopher@librehacker.com> writes:

> Hi, part of my work is researches/troubleshooting in a big 
> collection of old Fortran code files. I want to be able to use 
> the xref tools to help me. However, it seems that etags does not 
> tag Fortran variables, which 99% of the time is what I am 
> interested in. It looks like there is a way to tag anything you 
> want using regexps, so I was looking at the fortran.el code to 
> see if maybe I could find the magic regexp for this. But there 
> is a lot going on here in fortran.el that I don't understand yet 
> and I am wondering if somebody might be able to help me figure 
> this out.

Have you tried using xref in eglot? It will attempt to use the 
fortls fortran language server.

(I haven't tried this myself, but I've had good experiences with 
eglot and language servers in general.)

Cheers,

        - Joel



  parent reply	other threads:[~2024-08-07  2:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05 22:25 Tagging Fortran variables Christopher Howard
2024-08-06  6:26 ` Marcus Harnisch
2024-08-07  2:38 ` Joel Reicher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-06 16:31 Christopher Howard
2024-08-06 20:19 ` Marcus Harnisch
2024-08-07 17:31 Christopher Howard
2024-08-07 17:41 Christopher Howard
2024-08-08  7:05 ` Joel Reicher

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=8634nhawg1.fsf@gmail.com \
    --to=joel.reicher@gmail.com \
    --cc=christopher@librehacker.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.