Barry Warsaw wrote:
> On Dec 11, 2009, at 1:13 PM, Andreas Roehler wrote:
>
>> Already tried to tackle the issue. Works with GNU Emacs for me, not with
>> XEmacs until now.
>> Introduced some stuff from python.el - defconst
>> python-font-lock-syntactic-keywords etc.
>>
>> Patch attached - not p
Kent Borg wrote:
> Andreas Roehler wrote:
>> no need for that, emacs -q or emacs -Q is the right thing then
>>
>
> "emacs -q" does not work, "emacs -Q" does work. (The toggling of
> highlighting while opening and closing a multi-line comment is like
> before,
seems normal, seems the way it p
Andreas Roehler wrote:
> no need for that, emacs -q or emacs -Q is the right thing then
>
"emacs -q" does not work, "emacs -Q" does work. (The toggling of
highlighting while opening and closing a multi-line comment is like
before, but inside a correct multi-line comment, a new ' is happily
ign
On Dec 11, 2009, at 1:13 PM, Andreas Roehler wrote:
> Already tried to tackle the issue. Works with GNU Emacs for me, not with
> XEmacs until now.
> Introduced some stuff from python.el - defconst
> python-font-lock-syntactic-keywords etc.
>
> Patch attached - not polished yet, but works here s
Kent Borg wrote:
> Andreas Roehler wrote:
>> BTW which system/version/emacs you are using?
>
> kentb...@bottom:~$ emacs --version
> GNU Emacs 22.2.1
> Copyright (C) 2008 Free Software Foundation, Inc.
> GNU Emacs comes with ABSOLUTELY NO WARRANTY.
> You may redistribute copies of Emacs
> under the
On Dec 11, 2009, at 9:25 AM, Kent Borg wrote:
> Dropping the new one in place doesn't fix it, but I think I need to
> compile something...
FWIW, I run python-mode.el right out of a bzr checkout. I never byte compile
my personal elisp files any more. :)
-Barry
_
Kent Borg wrote:
> Dropping the new one in place doesn't fix it, but I think I need to
> compile something...
Follow up on my last e-mail...
OK, I think I compiled it:
kentb...@bottom:~$ ls -l
/usr/share/emacs/site-lisp/python-mode/python-mode.elc
-rw-r--r-- 1 root root 115028 2009-12-11 09:38
Andreas Roehler wrote:
> python-mode.el version 351 is in use.
I am not using that version. I dug around and downloaded 351.
Internally mine is versioned: "5.1.0", 351 says "5.1.0+".
kentb...@bottom:~$ diff
/usr/share/emacs/site-lisp/python-mode/python-mode.el
/home/kentborg/sw_downloads/pyth
Andreas Roehler wrote:
> BTW which system/version/emacs you are using?
kentb...@bottom:~$ emacs --version
GNU Emacs 22.2.1
Copyright (C) 2008 Free Software Foundation, Inc.
GNU Emacs comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of Emacs
under the terms of the GNU General Public L
On Dec 11, 2009, at 8:50 AM, s...@pobox.com wrote:
>
>Kent> Am I misunderstanding something?
>
> Perhaps. There is definitely a deficiency in the Emacs syntax table stuff,
> at least the way python-mode uses it. I believe the other Python mode (the
> one delivered with recent versions of G
Kent> Am I misunderstanding something?
Perhaps. There is definitely a deficiency in the Emacs syntax table stuff,
at least the way python-mode uses it. I believe the other Python mode (the
one delivered with recent versions of GNU Emacs) might handle triple-quoted
strings better.
In many c
Hello,
I recently started playing with using docstrings more fully and
discovered a problem. I can't use apostrophes in multi-line comments
without confusing python-mode.
For example:
> def my_sqrt(x):
> '''Computes squareroot.
>
> Note: This function doesn't know about imaginary number
12 matches
Mail list logo