From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: New completion mode
Date: Sun, 30 Apr 2006 11:32:32 +0200 [thread overview]
Message-ID: <m3bqujl87j.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <b4mzmibqrmw.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Thanks. However, the present ecomplete code seems to be written
> only for Emacs. In XEmacs 21.4, I tried making aliases of some
> missing functions, e.g., line-beginning-position, read-event,
> etc., but the goal seems to be far beyond such workarounds. (I
> wish I had time to grapple with it, though.)
I'll compile Gnus for XEmacs and try getting it to work there, too.
> [1] It is not only the case where the FOO-minor-mode variable
> indicates the status but also the case where we have to use some
> function or other like `message-tamago-not-in-use-p' to detect
> the condition. We are using indeed various tools to enter
> Japanese text. So, things we can do might be a few after all.
It's a difficult problem determining that 1) it was the user that
inserted something and 2) the user's insertion is "complete", in a
way. Some of the input methods in Emacs are pretty hairy...
>> What should the cookie look like?
>
> It will be a line which looks like the following put at the
> beginning of a file:
>
> ;;; .ecompleterc -*- mode: emacs-lisp; coding: iso-2022-7bit -*-
> ;; This file is generated automatically by ecomplete.el.
>
> However, it seems now to be unnecessary if `iso-2022-7bit' is
> used. Because both Emacs and XEmacs-Mule are successful in
> detecting the coding system automatically.
Ok; then I won't put the cookie into the file.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2006-04-30 9:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 10:30 Lars Magne Ingebrigtsen
2006-04-11 15:40 ` Sam Steingold
2006-04-11 15:52 ` Lars Magne Ingebrigtsen
2006-04-11 16:02 ` Sam Steingold
2006-04-12 6:21 ` Lars Magne Ingebrigtsen
2006-04-12 7:55 ` Lars Magne Ingebrigtsen
2006-04-12 11:13 ` Reiner Steib
2006-04-12 11:35 ` Lars Magne Ingebrigtsen
2006-04-12 13:25 ` Lars Magne Ingebrigtsen
2006-04-12 14:41 ` Lars Magne Ingebrigtsen
2006-04-13 2:29 ` Wolfram Fenske
2006-04-13 5:42 ` Lars Magne Ingebrigtsen
2006-04-13 16:19 ` Wolfram Fenske
[not found] ` <m3bqv6av4t.fsf-qBEgNjfYAPolG3ThADb//ti2O/JbrIOy@public.gmane.org>
2006-04-13 17:31 ` Jochen Küpper
2006-04-14 10:27 ` Lars Magne Ingebrigtsen
2006-04-16 19:50 ` Use of ecomplete.el in message.el (was: New completion mode) Reiner Steib
2006-04-16 20:30 ` Use of ecomplete.el in message.el Lars Magne Ingebrigtsen
2006-04-17 11:40 ` Reiner Steib
2006-04-17 13:04 ` Lars Magne Ingebrigtsen
2006-04-17 0:23 ` Steve Youngs
2006-04-17 9:01 ` Lars Magne Ingebrigtsen
2006-04-18 11:17 ` New completion mode Simon Josefsson
2006-04-18 13:04 ` Reiner Steib
2006-04-18 13:46 ` Simon Josefsson
2006-04-18 15:24 ` Lars Magne Ingebrigtsen
2006-04-18 21:07 ` Simon Josefsson
2006-04-21 23:51 ` Lars Magne Ingebrigtsen
2006-04-14 19:26 ` Miles Bader
2006-04-15 5:46 ` Lars Magne Ingebrigtsen
2006-04-18 22:22 ` Wolfram Fenske
2006-04-19 7:26 ` Katsumi Yamaoka
2006-04-20 12:14 ` Steve Youngs
2006-04-20 13:07 ` gnus-replace-in-string: Avoid inf-loop in XEmacs (was: New completion mode) Reiner Steib
2006-04-20 14:18 ` gnus-replace-in-string: Avoid inf-loop in XEmacs Michael Olson
2006-04-20 15:23 ` Reiner Steib
2006-04-22 4:36 ` Michael Olson
2006-04-20 16:06 ` Steve Youngs
2006-04-20 17:06 ` Reiner Steib
2006-04-21 6:32 ` New completion mode Steve Youngs
2006-04-22 0:01 ` Lars Magne Ingebrigtsen
2006-04-24 8:55 ` Katsumi Yamaoka
2006-04-30 9:32 ` Lars Magne Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bqujl87j.fsf@quimbies.gnus.org \
--to=larsi@gnus.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 NNTP newsgroup(s).