unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: c-submode-indicators at wrong place in minor-mode-alist
Date: Sat, 17 Dec 2005 09:03:56 +1300	[thread overview]
Message-ID: <17315.7596.987910.350766@kahikatea.snap.net.nz> (raw)
In-Reply-To: <Pine.LNX.3.96.1051216092403.548B-100000@acm.acm>

 > >The patch below seems to fix it for me.  I think I have associated each
 > >function with the right variable but these aren't really minor modes in
 > >the normal sense (if they were the functions and variables would have
 > >the same name).
 > 
 > OK.  Do you have any feel for how portable the fix is (In Emacs 20.n,
 > 21.n, XEmacs 21.4.n)?

I'm fairly sure it will work in Emacs 21.x but I don't know about the other
versions.  However, clearly the change could be commmitted to the Emacs
repository.  I don't how you store your changes, but a distributed RCS like
Arch, would seem ideal for your purposes. Then the changes that you commit to
Emacs 22.1 could be stored as a branch in your local repository.  I don't know
all the details (I've nwver used Arch) but Miles Bader keeps an Arch mirror
for Emacs and I'm sure he would put you in the picture.

 > >CC mode seems to have become much more complicated, but that might be
 > >because its much more powerful.  I don't know, I just find it hard to
 > >understand.
 > 
 > It is hard to understand.  Partly, it's because C and friends are such a
 > dreadful languages (to parse, that is ;-), partly because CC Mode handles
 > seven different languages in a single package.  It "jumped in complexity"
 > between releases 5.28 and 5.30 (Summer 2003).  It's probably more
 > accurate to say that the complexity has been concentrated in a few
 > hot-spots, allowing simplicity to pervade the rest.

You do most of the development.  It only needs to be simpler if you want to
look to others like emacs-devel, to help you.  One way to do that, I guess, is
to strip down the branch for Emacs 22.1 in your hypothetical Arch repository,
to just work in Emacs 22.1.

Nick


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click


  reply	other threads:[~2005-12-16 20:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 21:41 c-submode-indicators at wrong place in minor-mode-alist Stefan Monnier
2005-12-15  0:25 ` Nick Roberts
2005-12-15 14:25   ` Alan Mackenzie
2005-12-15 20:08     ` Nick Roberts
2005-12-16 10:18       ` Alan Mackenzie
2005-12-16 20:03         ` Nick Roberts [this message]
2005-12-17  8:22         ` Eli Zaretskii
2005-12-18  9:26           ` Alan Mackenzie
2005-12-15 20:40     ` Stefan Monnier
2005-12-16 10:57       ` Alan Mackenzie
2005-12-17  1:05         ` Richard M. Stallman

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=17315.7596.987910.350766@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).