-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- From reading emacs-devel, it seems that the python.el has made
changes to the mode and explicitly taken them out of the copyright
assignment for the FSF, so Emacs upstream can't include them.
So now we are at three different python modes for Emacs..
On Feb 03, 2011, at 09:23 PM, Georg Brandl wrote:
>- From reading emacs-devel, it seems that the python.el has made
>changes to the mode and explicitly taken them out of the copyright
>assignment for the FSF, so Emacs upstream can't include them.
>
>So now we are at three different python modes fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.02.2011 22:09, schrieb Barry Warsaw:
> On Feb 03, 2011, at 09:23 PM, Georg Brandl wrote:
>
>>- From reading emacs-devel, it seems that the python.el has made
>>changes to the mode and explicitly taken them out of the copyright
>>assignment for t
Georg> - From reading emacs-devel, it seems that the python.el has made
Georg> changes to the mode and explicitly taken them out of the
Georg> copyright assignment for the FSF, so Emacs upstream can't include
Georg> them.
Georg> So now we are at three different python modes fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.02.2011 22:13, schrieb s...@pobox.com:
>
> Georg> - From reading emacs-devel, it seems that the python.el has made
> Georg> changes to the mode and explicitly taken them out of the
> Georg> copyright assignment for the FSF, so Emacs
Barry> Wonderful.
Barry> http://thread.gmane.org/gmane.emacs.devel/135075
Wasn't a lot of our heartburn alwhile ago precipitated by Dave Love? He of
the massive-patch-which-must-not-be-divided? In fact, isn't he the original
author of the the python.el which *is* delivered with GNU Ema
Is there any reason not to highlight "lambda:" as a keyword, i.e. when
it's immediately followed by a colon? The patch below takes a stab at
that. I guess it might be ideal if the colon were not highlighted; I
didn't look into that.
Thanks very much for the python-mode code and please tell me if t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 03.02.2011 22:19, schrieb s...@pobox.com:
>
> Barry> Wonderful.
>
> Barry> http://thread.gmane.org/gmane.emacs.devel/135075
>
> Wasn't a lot of our heartburn alwhile ago precipitated by Dave Love? He of
> the massive-patch-which-must-not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Right, this has bothered me as well a few times. +1 for the patch.
Georg
Am 03.02.2011 20:10, schrieb Dan Davison:
> Is there any reason not to highlight "lambda:" as a keyword, i.e. when
> it's immediately followed by a colon? The patch below takes
On Thu, Feb 3, 2011 at 1:13 PM, wrote:
>
>Georg> - From reading emacs-devel, it seems that the python.el has made
>Georg> changes to the mode and explicitly taken them out of the
>Georg> copyright assignment for the FSF, so Emacs upstream can't include
>Georg> them.
>
>Georg>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Feb 03, 2011, at 10:13 PM, Georg Brandl wrote:
>Would we be able to find all the contributors and get them to sign papers
>for the FSF? Otherwise there's no need to even think about that step.
At one point in the distant past we *did* that and
>> Would we be able to find all the contributors and get them to sign
>> papers for the FSF? Otherwise there's no need to even think about
>> that step.
Barry> At one point in the distant past we *did* that and sent it to the
Barry> FSF (IIRC, Tim Peters, Ken M. and myself at
On Feb 03, 2011, at 07:10 PM, Dan Davison wrote:
>Is there any reason not to highlight "lambda:" as a keyword, i.e. when
>it's immediately followed by a colon? The patch below takes a stab at
>that. I guess it might be ideal if the colon were not highlighted; I
>didn't look into that.
Nope, it's
13 matches
Mail list logo