unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Pogonyshev <pogonyshev@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: `etags' bug?
Date: Wed, 15 Dec 2004 04:57:32 +0200	[thread overview]
Message-ID: <200412150457.32970.pogonyshev@gmx.net> (raw)
In-Reply-To: <E1CeAIh-00051n-00@pot.isti.cnr.it>

> >It seems that behaviour of `etags' is broken.
>
> Dear Paul, I cannot reproduce the behaviour you observe, neither with
> the stock emacs 21.3 etags nor with the latest etags in the CVS.  It may
> be a platform-dependent bug; I use a Debian system running on i686.
>
> Before going on to debug it, make sure you are indeed using the latest
> version:
>
> $ strings ../etags|fgrep 'pot rev'
> @(#) pot revision number is 17.5
>
> and try to recompile it from scratch, to reduce the possibility that you
> used some unstable library or similar problems.
>
> If you can reproduce the bug with this version, please contact me, so we
> can find a way to debug this.

I refreshed my CVS working directory and recompiled with optimizations
turned off (`CFLAGS="-g"'.)  The behaviour didn't change.

I tried a little debugging and I don't understand how the behaviour could
be as documented.  Function main() basically looks like this:

  while ((opt = getopt_long (...)) != EOF)
    switch (opt)
      {
        /* store `--language' and `--regex' arguments in `argbuffer' */
      }

  for (; optind < argc; optind++)
    {
      /* store filenames in `argbuffer' */
    }

Now, I cannot understand how this code can distinguish between

        --language none file1 --language auto file2

and

	--language none --language auto file1 file2

_in principle_.

Yet in the man page we have

	-l language, --language=language
		Parse  the  following  files  according  to  the  given
		       ^^^^^^^^^^^^^^^^^^^^^
		language.  More than one such options may be intermixed
		with  filenames.   Use --help  to  get  a  list of  the
		available   languages   and   their  default   filename
		extensions.  The `auto' language can be used to restore
		automatic detection of language based on the file name.
		The  `none' language  may be  used to  disable language
		parsing  altogether; only  regexp matching  is  done in
		this case (see the --regex option).

Maybe I'm really missing something fundamental.

Paul

  reply	other threads:[~2004-12-15  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 18:15 `etags' bug? Paul Pogonyshev
2004-12-14 10:53 ` Francesco Potorti`
2004-12-15  2:57   ` Paul Pogonyshev [this message]
2004-12-15 13:19     ` Andreas Schwab
2004-12-15 13:46       ` Francesco Potorti`
2004-12-15 15:45         ` Paul Pogonyshev

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=200412150457.32970.pogonyshev@gmx.net \
    --to=pogonyshev@gmx.net \
    --cc=emacs-devel@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 public inbox

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

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