From: Dave Love <fx@domain.invalid>
Subject: Re: Problems with built-in Python mode of Emacs22 on w32
Date: Wed, 12 Apr 2006 12:18:31 +0100 [thread overview]
Message-ID: <rzq1ww359fc.fsf@loveshack.ukfsn.org> (raw)
In-Reply-To: 1144504450.570708.26150@e56g2000cwe.googlegroups.com
"Anton V. Belyaev" <anton.belyaev@gmail.com> writes:
> I searched the group, but it seems nobody encountered such a problem.
Well it's not the correct place to report such problems, not that
reporting them correctly gets Emacs' Python support fixed :-(.
The version at <URL:http://www.loveshack.ukfsn.org/emacs/> fixes this
and other things. I don't know whether it's possible easily to make
completion work under MS Windows.
prev parent reply other threads:[~2006-04-12 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-08 13:54 Problems with built-in Python mode of Emacs22 on w32 Anton V. Belyaev
2006-04-08 15:57 ` Eli Zaretskii
[not found] ` <mailman.201.1144511871.9609.help-gnu-emacs@gnu.org>
2006-04-08 20:01 ` Anton V. Belyaev
2006-04-10 5:09 ` Stefan Monnier
2006-04-10 8:30 ` Alan Mackenzie
2006-04-12 11:18 ` Dave Love [this message]
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=rzq1ww359fc.fsf@loveshack.ukfsn.org \
--to=fx@domain.invalid \
--cc=fx@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.
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).