all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)
To: Eli Zaretskii <eliz@gnu.org>
Subject: bug#3101: marked as done (23.0.92; Emacs manual, node Tags)
Date: Sat, 25 Apr 2009 07:30:05 +0000	[thread overview]
Message-ID: <handler.3101.D3101.12406442235866.ackdone@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: 007501c9c51c$5a6c8f70$0200a8c0@us.oracle.com

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]


Your message dated Sat, 25 Apr 2009 10:23:34 +0300
with message-id <83skjxfb7t.fsf@gnu.org>
and subject line Re: bug#3101: 23.0.92; Emacs manual, node Tags
has caused the Emacs bug report #3101,
regarding 23.0.92; Emacs manual, node Tags
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3101: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3101
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 3814 bytes --]

From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: 23.0.92; Emacs manual, node Tags
Date: Fri, 24 Apr 2009 13:36:31 -0700
Message-ID: <007501c9c51c$5a6c8f70$0200a8c0@us.oracle.com>

The first sentence of this node doesn't sound right to me. At least
it's not clear what is meant.
 
  "A "tags table" is a description of how a multi-file
   program is broken up into files."
 
A multi-file program? What program would that be? There is no further
mention of this.  I don't understand this sentence, and I cannot
imagine how it describes what a tags table is.
 
Also confusing is the part that starts "When a file parsed by `etags'
is generated from a different source file, like a C file generated
from a Cweb source file,..." To understand this (and I don't), a
reader needs to already understand what `etags' is and what its
parsing amounts to, and s?he needs to know what Cweb is (I don't). Not
to mention that it is mysterious what is meant by "a different source
file" - different from what?
 
One cannot understand this text without knowing how tags work, the
role of "source files" in that, and so on. IOW, this doesn't help; it
confuses.
 

In GNU Emacs 23.0.92.1 (i386-mingw-nt5.1.2600)
 of 2009-03-30 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
 




[-- Attachment #3: Type: message/rfc822, Size: 3126 bytes --]

From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, 3101-done@emacsbugs.donarmstrong.com
Subject: Re: bug#3101: 23.0.92; Emacs manual, node Tags
Date: Sat, 25 Apr 2009 10:23:34 +0300
Message-ID: <83skjxfb7t.fsf@gnu.org>

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Fri, 24 Apr 2009 13:36:31 -0700
> Cc: 
> 
> The first sentence of this node doesn't sound right to me. At least
> it's not clear what is meant.
>  
>   "A "tags table" is a description of how a multi-file
>    program is broken up into files."
>  
> A multi-file program? What program would that be? There is no further
> mention of this.  I don't understand this sentence, and I cannot
> imagine how it describes what a tags table is.

I changed this to

    A @dfn{tags table} is a description of how program's sources are
  broken up into individual source files.

I hope this is more clear.

> Also confusing is the part that starts "When a file parsed by `etags'
> is generated from a different source file, like a C file generated
> from a Cweb source file,..." To understand this (and I don't), a
> reader needs to already understand what `etags' is and what its
> parsing amounts to, and s?he needs to know what Cweb is (I don't). Not
> to mention that it is mysterious what is meant by "a different source
> file" - different from what?

The text reads now

    Each entry in the tags table records the name of a tag, the name of
  the file that the tag is defined in (implicitly), and the position in
  that file of the tag's definition.  If the file is a generated file,
  its tags reference the originating source file.  Examples of generated
  files include C files generated from Cweb source files or from a Yacc
  parser or Lex scanner definitions, @file{.i} preprocessed C files, and
  Fortran files produced by preprocessing @file{.fpp} source files.

OK?


      reply	other threads:[~2009-04-25  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <83skjxfb7t.fsf@gnu.org>
2009-04-24 20:36 ` bug#3101: 23.0.92; Emacs manual, node Tags Drew Adams
2009-04-25  7:30   ` Emacs bug Tracking System [this message]

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=handler.3101.D3101.12406442235866.ackdone@emacsbugs.donarmstrong.com \
    --to=owner@emacsbugs.donarmstrong.com \
    --cc=eliz@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.