unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: dapfy@t-online.de (Daniel Pfeiffer)
Cc: bug-gnu-emacs@gnu.org
Subject: Re: CPerl mode cleaned up
Date: Wed, 12 Feb 2003 22:36:06 +0100	[thread overview]
Message-ID: <20030212223606.2ab59cc2.occitan@esperanto.org> (raw)
In-Reply-To: <E18j3aB-0005JM-00@fencepost.gnu.org>

Ilya Zakharevich <ilya@Math.Berkeley.EDU> skribis:
> On Wed, Feb 12, 2003 at 12:11:31AM +0100, Daniel Pfeiffer wrote:
> > Therefore I have updated both the copyright and version number to 4.33.
> but please read the docstring for the version number!  If you change
> the meaning of the number, please change the name of the variable too.

Actually I changed it according to the name, but the doc string is
inconsistent with the name.

Richard Stallman <rms@gnu.org> skribis:
>     the version of CPerl mode seems utter chaos.  Both Emacs and Ilya's web-site
>     have 4.32, but they are very different.  While Emacs' newest copyright is
>     much older, CVS with its many little fixes, shows that the opposite is true.

> Having version numbers in Lisp packages causes persistent problems
> which persistently waste time.

> In the past my solution was to delete the version numbers from Lisp
> packages.  They are redundant anyway, because each Emacs version comes
> with on particular version of every Lisp file.

That is my feeling too.  Given the recent discussion on gnu.emacs.help,
people don't read the doc of a variable called something-version.  They just
assume that to be the version.

Ilya, you should say whether you plan to further develop cperl (from the
history of your ftp-site, I doubt it).  And if you do, it would be a good
idea to develop the Emacs CVS version.  Then the version number can be
eliminated without confusion.

Also, I found your email as written in the module to be defunct.  It should
be updated in the module to the one above.

Richard, will you do those two little changes?  No need to resend that huge
diff, is there?  The variable also gets shown from an easymenu entry which
should be eliminated.

coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer

-- GPL 3: take the wind out of Palladium's sails! --
 ------
  -- My other stuff here too, sawfish, make.pl...: --
   ------
    -- http://dapfy.bei.t-online.de/ --

  reply	other threads:[~2003-02-12 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-11 23:11 CPerl mode cleaned up Daniel Pfeiffer
2003-02-12  5:06 ` Ilya Zakharevich
2003-02-12 20:34 ` Richard Stallman
2003-02-12 21:36   ` Daniel Pfeiffer [this message]
2003-02-13 22:17     ` Ilya Zakharevich

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=20030212223606.2ab59cc2.occitan@esperanto.org \
    --to=dapfy@t-online.de \
    --cc=bug-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.
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).