From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: asking for advice for changing the cfengine.el progmode to support CFEngine 3.x
Date: Fri, 01 Jul 2011 05:15:47 -0500 [thread overview]
Message-ID: <87oc1e8fxo.fsf@lifelogs.com> (raw)
In-Reply-To: 838vsis990.fsf@gnu.org
On Fri, 01 Jul 2011 11:19:55 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> Because cfengine.el is in the trunk. It doesn't make sense to put the
>> two files in different places--it's confusing for the users, they'll see
>> one and won't know about the other. I also can't merge cfengine.el with
>> cfengine3.el, they are too different and the new code is IMHO much
>> simpler and cleaner.
EZ> I see you committed it already. However, cfengine3.el clashes with
EZ> cfengine.el in the 8+3 file namespace, so please rename it, if you
EZ> don't want to follow Stefan's advice and merge them into a single file
EZ> (which I personally think is TRT).
I realized I could just do that, even though `cfengine3-mode' remains a
separate function. So I moved `cfengine3-mode' to cfengine.el and
abstracted the common functionality; I then removed cfengine3.el.
Ted
next prev parent reply other threads:[~2011-07-01 10:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 18:11 asking for advice for changing the cfengine.el progmode to support CFEngine 3.x Ted Zlatanov
2011-06-17 22:02 ` Stefan Monnier
2011-06-20 20:42 ` Ted Zlatanov
2011-06-21 14:59 ` Stefan Monnier
2011-06-21 19:26 ` Ted Zlatanov
2011-06-22 17:44 ` Stefan Monnier
2011-06-22 21:24 ` Ted Zlatanov
2011-06-23 21:31 ` Ted Zlatanov
2011-06-27 15:44 ` Ted Zlatanov
2011-06-30 12:47 ` Ted Zlatanov
2011-06-30 16:03 ` Stefan Monnier
2011-06-30 18:25 ` Ted Zlatanov
2011-06-30 21:10 ` Stefan Monnier
2011-06-30 21:29 ` Ted Zlatanov
2011-07-01 8:19 ` Eli Zaretskii
2011-07-01 10:15 ` Ted Zlatanov [this message]
2011-07-01 11:22 ` Eli Zaretskii
2011-07-01 13:03 ` Ted Zlatanov
2011-06-30 16:11 ` Stefan Monnier
2011-06-30 18:28 ` Ted Zlatanov
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=87oc1e8fxo.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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 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.