unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
Cc: bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: man/cc-mode.ss.
Date: Sun, 1 May 2005 14:38:28 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1050501142507.224A-100000@acm.acm> (raw)
In-Reply-To: <87oecj517w.fsf@xs4all.nl>

Hi, Lute!

On Tue, 12 Apr 2005, Lute Kamstra wrote:

>Richard Stallman <rms@gnu.org> writes:

>>     The "@define ss" seems to create the cc-mode.ss file when the dvi
>>     file is made.  It stays empty because of the "@syncodeindex ss
>>     cp", though.

>> Does it work to delete that @define?

>Creating a dvi file still works, but makeinfo fails to create info and
>html files:

>  cc-mode.texi:61: Unknown index `ss' and/or `cp' in @synindex.
>  cc-mode.texi:3477: Unknown command `ssindex'.
>  ...

>So the patch below should do what we want.

Hang on a mo', that's our file!

Would it be possible to cc CC Mode (at bug-cc-mode@gnu.org) with things
like this, so that we can keep the definitive copy at sourceforge up to
date?

I only saw this thread this morning when I was garbage collecting my
emacs-devel archive.  emacs-devel is a very busy list, much more so than
bug-cc-mode, and it's easy to miss important stuff there when one is just
scanning it rather than reading it intensely.

As a matter of interest, cc-mode.texi is undergoing substantial revision,
and it is thus likely that patches made to a current version can't be
applied automatically to the HEAD version (though this particular patch
might - I haven't tried it yet).

Thanks in advance!

>Lute.


>Index: cc-mode.texi
>===================================================================
>RCS file: /cvsroot/emacs/emacs/man/cc-mode.texi,v
>retrieving revision 1.27
>diff -c -r1.27 cc-mode.texi
>*** cc-mode.texi	9 Feb 2005 15:50:35 -0000	1.27
>--- cc-mode.texi	12 Apr 2005 17:53:10 -0000
>***************
>*** 55,61 ****
>--- 55,63 ----
>  @comment !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

>  @comment Define an index for syntactic symbols.
>+ @ifnottex
>  @defindex ss
>+ @end ifnottex

>  @comment Combine key, syntactic symbol and concept indices into one.
>  @syncodeindex ss cp

-- 
Alan Mackenzie (Munich, Germany)

  parent reply	other threads:[~2005-05-01 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 16:22 man/cc-mode.ss Lute Kamstra
2005-04-12  2:59 ` man/cc-mode.ss Richard Stallman
2005-04-12  8:23   ` man/cc-mode.ss Lute Kamstra
2005-04-12 17:24     ` man/cc-mode.ss Richard Stallman
2005-04-12 17:55       ` man/cc-mode.ss Lute Kamstra
2005-04-13 18:31         ` man/cc-mode.ss Richard Stallman
2005-05-01 14:38         ` Alan Mackenzie [this message]
2005-05-01 23:39           ` man/cc-mode.ss Richard Stallman
2005-05-09  9:47           ` man/cc-mode.ss Lute Kamstra
2005-05-09 18:48             ` man/cc-mode.ss Alan Mackenzie

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=Pine.LNX.3.96.1050501142507.224A-100000@acm.acm \
    --to=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --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).