all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Richard G Riley <rileyrgdev@googlemail.com>
Cc: Richard G Riley <rileyrgdev@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: code completion
Date: Wed, 12 Mar 2008 12:06:17 +0000	[thread overview]
Message-ID: <878x0o87uu.fsf@bzg.ath.cx> (raw)
In-Reply-To: <ct8x0ory2w.fsf@richardriley.net> (Richard G. Riley's message of "Wed, 12 Mar 2008 12:17:11 +0100")

Richard G Riley <rileyrgdev@googlemail.com> writes:

> However, it would be wrong to say all is flowers and sunshine. It is not
> and an honest answer (from my perspective) is more respectful at times.

If someone requests improvements for a feature in Emacs (e.g. code
refactoring) it is honest to tell about the shortcomings of its current
implementation.  It is depressing to recommand the OP to have a look at
other editors, not because it is dishonest, but because such an advice
won't help make the Emacs implementation better.

And the more constructive way is to give directions on how to help
improving the feature.

Imagine this: you create a new tool (say bzr) that aims at being better
than others (say CVS, RCS) wrt some features.  When you start coding the
tool, it is still behind the other ones.  Now imagine that someone likes
your tool and asks about a feature.  What if someone else recommends the
OP to switch to another tool, just because your tool (the one he uses)
doesn't have this feature ?

I guess you woudn't find this constructive...

-- 
Bastien




  reply	other threads:[~2008-03-12 12:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.8709.1205244459.18990.help-gnu-emacs@gnu.org>
2008-03-11 15:56 ` code completion Richard G Riley
2008-03-11 19:50   ` Eli Zaretskii
2008-03-11 21:07     ` Lennart Borgman (gmail)
2008-03-12  4:14       ` Eli Zaretskii
     [not found]     ` <mailman.8726.1205269686.18990.help-gnu-emacs@gnu.org>
2008-03-11 21:15       ` Richard G Riley
2008-03-12  9:56       ` Arne Schmitz
2008-03-12 19:37         ` Óscar Fuentes
     [not found]         ` <mailman.8785.1205350636.18990.help-gnu-emacs@gnu.org>
2008-03-12 19:51           ` Pascal Bourguignon
2008-03-12 20:58             ` Tom Tromey
2008-03-12 22:22               ` Lennart Borgman (gmail)
2008-03-12 21:35                 ` Tom Tromey
2008-03-12 23:17                   ` Lennart Borgman (gmail)
2008-03-12 23:24                     ` Jason Rumney
2008-03-13  0:14                       ` Óscar Fuentes
2008-03-12 21:40             ` Óscar Fuentes
     [not found]   ` <mailman.8721.1205265045.18990.help-gnu-emacs@gnu.org>
2008-03-11 21:05     ` Richard G Riley
2008-03-12  4:19       ` Eli Zaretskii
     [not found]       ` <mailman.8740.1205295602.18990.help-gnu-emacs@gnu.org>
2008-03-12  4:55         ` Richard G Riley
2008-03-12  9:11       ` Bastien Guerry
2008-03-12 11:17         ` Richard G Riley
2008-03-12 12:06           ` Bastien [this message]
2008-03-12 12:29             ` Richard G Riley
2008-03-12 13:07               ` Bastien Guerry
2008-03-12 16:06                 ` Richard G Riley
2008-03-11 14:08 Alain Muls
2008-03-11 19:36 ` Eli Zaretskii
2008-03-12  9:06 ` Bastien
     [not found] ` <mailman.8747.1205313317.18990.help-gnu-emacs@gnu.org>
2008-03-12 11:23   ` Richard G Riley
2008-03-12 12:07     ` Bastien Guerry
2008-03-12 12:30       ` Richard G Riley
2008-03-12 13:10         ` Bastien Guerry
     [not found] <mailman.3235.1151043305.9609.help-gnu-emacs@gnu.org>
2006-06-23 18:45 ` Code completion Boof
2006-06-23 20:03   ` Thorsten Bonow
2006-06-24 23:45     ` Jorge Peixoto de Morais Neto
  -- strict thread matches above, loose matches on Subject: below --
2006-06-23  6:14 Jorge Peixoto de Morais Neto
2006-06-23 20:34 ` Noah Slater

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=878x0o87uu.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rileyrgdev@gmail.com \
    --cc=rileyrgdev@googlemail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.