From: Jorgen Grahn <grahn+nntp@snipabacken.se>
To: help-gnu-emacs@gnu.org
Subject: Re: C-x C-b (switch-to-buffer) smarter suggestions?
Date: 11 Feb 2010 18:59:35 GMT [thread overview]
Message-ID: <slrnhn8ksn.1qf.grahn+nntp@frailea.sa.invalid> (raw)
In-Reply-To: mailman.926.1265729432.14305.help-gnu-emacs@gnu.org
On Tue, 2010-02-09, Richard Riley wrote:
> Jorgen Grahn <grahn+nntp@snipabacken.se> writes:
>
>> On Mon, 2010-02-08, Stefan Monnier wrote:
>>>> Let's say I have a dozen buffers, including foo.c and foo.h. I am in
>>>> foo.c but I want to jump to foo.h. So I do
>>>
>>>> C-x C-b foo TAB
>>>
>>>> But this doesn't complete to foo.h, because foo.c is also an
>>>> alternative -- even though that's the buffer I'm explicitly trying to
>>>> switch *from*.
>>>
>>> Apparently, you haven't yet upgraded to Emacs-23.
>>
>> So you're implying that Emacs 23 fixes exactly that, or that it
>> reworks the buffer selection interface completely?
>>
>> Actually I still use Emacs 21. Emacs 22 is also available as part of
>> Debian Linux, but I gain more by sticking to 21, which is the one
>> available at work (semi-officially available -- officially we are
>> stuck with 20).
>
> Interesting. I find it astonishing that anyone would insist on using
> such an old version. Are your customisations so incompatible with newer
> Emacs? The call of the daemon and anti aliased fonts would be enough to
> move for most .. Or do you just have an intransigent BOFH?
I don't know, but for the Emacs 20 part (20.7, installed on Solaris in
2000 according to time stamps) my guess is a combination of:
- lack of attention to the Solaris environment when more and more
work is done on Linux
- outsourcing of BOFH activities
- hard to know what problems an upgrade would cause for hundreds of
users; hard to know exactly *who* they are and what features they
have come to rely on
- maintaining an existing development environment = bad career move;
implementing new, complex, proprietary and expensive = good move
- the programmers who really care install their own newer Emacs and
tell noone about it
- Emacs 20 is still a very good text editor
I don't think it's uncommon for organizations to end up in that
situation, unfortunately. But I wouldn't want to live at the bleeding
edge either ...
/Jorgen
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
next prev parent reply other threads:[~2010-02-11 18:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 8:03 C-x C-b (switch-to-buffer) smarter suggestions? Jorgen Grahn
2010-02-07 8:47 ` Alberto Luaces
[not found] ` <mailman.826.1265532477.14305.help-gnu-emacs@gnu.org>
2010-02-07 22:54 ` Jorgen Grahn
2010-02-08 2:11 ` Stefan Monnier
2010-02-08 12:17 ` Jorgen Grahn
2010-02-08 17:38 ` Stefan Monnier
2010-02-08 18:23 ` Teemu Likonen
2010-02-11 10:35 ` Jorgen Grahn
2010-02-11 14:48 ` Richard Riley
2010-02-09 15:15 ` Richard Riley
[not found] ` <mailman.926.1265729432.14305.help-gnu-emacs@gnu.org>
2010-02-11 18:59 ` Jorgen Grahn [this message]
2010-02-08 5:55 ` Dmitri Minaev
[not found] ` <mailman.852.1265608552.14305.help-gnu-emacs@gnu.org>
2010-02-08 11:45 ` Jorgen Grahn
2010-02-10 6:16 ` Dmitri Minaev
2010-02-09 4:46 ` Kevin Rodgers
[not found] ` <mailman.897.1265690809.14305.help-gnu-emacs@gnu.org>
2010-02-11 22:45 ` Jorgen Grahn
2010-02-12 4:42 ` Kevin Rodgers
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=slrnhn8ksn.1qf.grahn+nntp@frailea.sa.invalid \
--to=grahn+nntp@snipabacken.se \
--cc=help-gnu-emacs@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).