From: Richard Riley <rileyrgdev@googlemail.com>
To: Barry Warsaw <barry@python.org>
Cc: python-mode@python.org, Richard Riley <rileyrgdev@googlemail.com>,
Xavier, help-gnu-emacs@gnu.org
Subject: Re: python setup ?
Date: Mon, 04 May 2009 18:57:46 +0200 [thread overview]
Message-ID: <49ff1e8a.0407560a.7f38.137e@mx.google.com> (raw)
In-Reply-To: <CAA3F59D-282D-4257-91B5-1BBAB661900E@python.org> (Barry Warsaw's message of "Thu, 30 Apr 2009 09:24:46 -0400")
Barry Warsaw <barry@python.org> writes:
> On Apr 30, 2009, at 3:25 AM, Andreas Röhler wrote:
>
>> With python-mode.el, people may have good reasons, to
>> use it as it is - and me to leave it as it is. Thats
>> fine with bazaar and other DVCs, we can do that. My
>> branch doesn't hamper the origin and any further branch
>> will not. Its just freedom to try and see.
>
> This is true, and experimentation a good thing in the short term. In
> the long term though, a proliferation of branches just confuses people
> because no one's sure which is the official branch. Our lives are
> more difficult too because of the python-mode.el/python.el split.
>
> So I encourage you to experiment and get user feedback. Old-timers
> (and remember, python-mode.el's been in widespread use for 15 years)
> will be wedded to their muscle memory, but if you introduce a user-
> visible change that people like, they can be made configurable with
> defaults providing the old behavior. Then it will be possible to
> merge your changes back into the official branch. If you modularize
> your changes, then the less controversial ones can get merged in sooner.
>
> -Barry
>
>
IMO any new "obviously useful" features should be enabled by
default. Old Timers should have no problem reverting to older
configurations via settings. A point which generates much contention I
know. As it is, Python set up is/was a minefield. I have a reasonable
set up here fwiw,
This includes pysmell completions for hippie expand and company-mode.
http://richardriley.net/projects/emacs/dotprogramming#sec-1.3
next prev parent reply other threads:[~2009-05-04 16:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904280634.n3S6YctW009278@zogzog.maillard.mobi>
2009-04-30 7:25 ` python setup ? Andreas Röhler
2009-04-30 13:24 ` Barry Warsaw
2009-05-04 16:57 ` Richard Riley [this message]
2009-04-29 22:25 Xavier Maillard
-- strict thread matches above, loose matches on Subject: below --
2009-04-29 22:25 Xavier Maillard
2009-04-30 5:42 ` Andreas Röhler
[not found] <mailman.6159.1240901979.31690.help-gnu-emacs@gnu.org>
2009-04-28 16:56 ` Richard Riley
2009-05-13 21:05 ` Piet van Oostrum
[not found] <mailman.6155.1240900544.31690.help-gnu-emacs@gnu.org>
2009-04-28 16:55 ` Richard Riley
2009-04-28 6:34 Xavier Maillard
2009-04-28 6:34 Xavier Maillard
2009-04-28 6:34 Xavier Maillard
2009-04-28 8:04 ` thierry.volpiatto
2009-04-28 6:34 Xavier Maillard
2009-04-28 6:42 ` thierry.volpiatto
2009-04-28 8:51 ` Andreas Röhler
[not found] <mailman.6045.1240741475.31690.help-gnu-emacs@gnu.org>
2009-04-26 11:25 ` Richard Riley
2009-04-26 13:16 ` Richard Riley
2009-04-27 7:42 ` Andreas Röhler
[not found] ` <mailman.6094.1240818145.31690.help-gnu-emacs@gnu.org>
2009-04-27 8:53 ` Richard Riley
2009-04-27 11:08 ` Andreas Röhler
[not found] ` <mailman.6098.1240830481.31690.help-gnu-emacs@gnu.org>
2009-04-27 11:15 ` Richard Riley
2009-04-27 13:50 ` thierry.volpiatto
[not found] ` <mailman.6107.1240840677.31690.help-gnu-emacs@gnu.org>
2009-04-27 14:12 ` Richard Riley
2009-04-27 15:23 ` thierry.volpiatto
[not found] ` <mailman.6113.1240846261.31690.help-gnu-emacs@gnu.org>
2009-04-28 0:55 ` superbobry
2009-04-28 10:43 ` Bernardo
[not found] ` <mailman.6165.1240915318.31690.help-gnu-emacs@gnu.org>
2009-04-28 11:25 ` superbobry
2009-04-27 8:58 ` Richard Riley
2009-04-27 11:20 ` Andreas Röhler
[not found] ` <49f5b71c.0305560a.6147.25ed@mx.google.com>
2009-05-08 9:16 ` Andreas Röhler
[not found] ` <mailman.6842.1241774145.31690.help-gnu-emacs@gnu.org>
2009-05-08 16:36 ` Richard Riley
2009-05-01 21:35 ` bbbscarter
2009-04-26 10:25 Xavier Maillard
2009-04-26 11:29 ` thierry.volpiatto
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=49ff1e8a.0407560a.7f38.137e@mx.google.com \
--to=rileyrgdev@googlemail.com \
--cc=barry@python.org \
--cc=help-gnu-emacs@gnu.org \
--cc=python-mode@python.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.
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).