From: Luca Ferrari <fluca1978@infinito.it>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: etags and php classes
Date: Wed, 2 Apr 2014 08:40:26 +0200 [thread overview]
Message-ID: <CAKoxK+6U3D-9C9+udAF9cHey9MJcRN4VohKXr-fGuoPYTn_xCg@mail.gmail.com> (raw)
I've a project made of several php files, some procedural and some OOP.
I ran etags on the whole set of files, and while functions are mapped
well, classes and their members are not at all.
I've tried also to add the --member option to etags, but nothing changed:
etags -l php --members `find . -name '*.php'`
Am I missing something?
Thanks,
Luca
next reply other threads:[~2014-04-02 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 6:40 Luca Ferrari [this message]
2014-04-02 16:03 ` etags and php classes Eli Zaretskii
2014-04-03 6:27 ` Luca Ferrari
2014-04-03 9:47 ` Chris Van Dusen
2014-04-03 15:22 ` Luca Ferrari
2014-04-03 18:00 ` cavd
2014-04-03 23:45 ` Leo Liu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKoxK+6U3D-9C9+udAF9cHey9MJcRN4VohKXr-fGuoPYTn_xCg@mail.gmail.com \
--to=fluca1978@infinito.it \
--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.
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).