Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <steve@sxemacs.org>
Subject: Why I've stopped using ecomplete
Date: Fri, 28 Apr 2006 00:52:23 +1000	[thread overview]
Message-ID: <microsoft-free.87mze7jck8.fsf@youngs.au.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]

I think the two main reasons are that it simply doesn't fit into my
usage patterns, and it appears to not do anything useful in
(S)XEmacs.

I had it enabled for a week or thereabouts and in that time it
collected 13 addresses.  Of that 13, 3 were my own address for testing
the thing, another 7 were from mailing lists and so useless as
gnus-parameters takes care of those.  That left 3 possibly useful
ones.  Well, not, that useful, these 3 were already in my BBDB. :-)

The only thing I ever saw ecomplete do was to display the first match
in the echo area.  I could not find a way to make it either cycle or
display other matches.  And I could not find a way to make it put
anything in the To: header for me.  Is it supposed to?  I would have
thought so.

But what really killed it for me... was that enabling ecomplete
disables abbrev-mode in message-mode.  Man, I can't live without my
abbrevs. :-)

I did notice that if the addresses are collected with a ENT-enabled[1]
SXEmacs I got errors in non-ENT SXEmacsen.[2]

Lars, I hope you find this feedback useful.  And yeah, I'm happy to
test future versions. :-)


Footnotes: 
[1]  XEmacs equiv is "bignum" (21.5 only)

[2]  I think I mentioned this in another thread.

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|                 I am Dyslexic of Borg.                   | 
|    Fusistance is retile. Your arse will be laminated.    |
|------------------------------------<steve@sxemacs.org>---|

[-- Attachment #2: Type: application/pgp-signature, Size: 257 bytes --]

             reply	other threads:[~2006-04-27 14:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27 14:52 Steve Youngs [this message]
2006-04-28 19:16 ` Wes Hardaker
2006-04-30 10:33   ` Lars Magne Ingebrigtsen
     [not found]     ` <m3fyjv2vzv.fsf-qBEgNjfYAPolG3ThADb//ti2O/JbrIOy@public.gmane.org>
2006-04-30 11:18       ` Jochen Küpper
2006-04-30 11:34         ` Lars Magne Ingebrigtsen
2006-04-30 19:45         ` Ronan Waide
2006-04-30 20:16           ` Lars Magne Ingebrigtsen
2006-05-01  0:26             ` Dave Goldberg
2006-05-01  8:56               ` Reiner Steib
2006-05-01 11:47                 ` Lars Magne Ingebrigtsen
2006-05-01 16:34                   ` Jesper Harder
2006-05-02  6:59                   ` Bjørn Mork
2006-05-03  1:44                     ` Dave Goldberg
2006-05-03  8:06                       ` Bjørn Mork
2006-05-03 14:36             ` Mark Plaksin
2006-05-03 16:24               ` Lars Magne Ingebrigtsen
2006-05-03 17:04                 ` Mark Plaksin
2006-04-30 10:31 ` Lars Magne Ingebrigtsen

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=microsoft-free.87mze7jck8.fsf@youngs.au.com \
    --to=steve@sxemacs.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).