unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: CEDET non-regression bug fixes
Date: Wed, 14 Nov 2012 16:16:48 -0500	[thread overview]
Message-ID: <jwv1ufv28mg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <876258rp28.fsf@engster.org> (David Engster's message of "Wed, 14 Nov 2012 19:56:31 +0100")

>>> +  (with-selected-window (get-buffer-window "*Completions*")
>>> +    (if (posn-at-point (point-max))
>>> +	(goto-char (point-min))
>>> +      (scroll-up))))
>> This will signal an error when *Completions* is not displayed anywhere.

Actually, it's worse: it will signal an error when *Completions* is not
displayed in the selected frame.  IOW in my config it will always signal
an error.

> At this stage, there must be a *Completions* buffer, otherwise it's an
> error anyway. But regarding the freeze, I will wrap something around
> that making sure it exists.

I'd rather keep this for trunk:
- it's not safe.
- It's not a regression.
- It's not even a bug fix: it improves behavior more than it fixes a bug.

>>> -		   (buff (get-file-buffer file))
>>> +		   (buff (find-buffer-visiting file))
>> We need to do something to avoid those problems.  AFAIK there's no
>> reason to ever prefer get-file-buffer over find-buffer-visiting, so
>> maybe we should simply get rid of get-file-buffer and make it an alias
>> of find-buffer-visiting.
> Oh, you have my vote for that.

Great!  How much (time and effort) are you willing to contribute to
my campaign?

> But I have a hunch you won't put this change into the emacs-24 branch,

Huh?  How did you guess?

> so I read this comment as "Fine, please commit". ;-)

Indeed,


        Stefan



  reply	other threads:[~2012-11-14 21:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 20:52 CEDET non-regression bug fixes David Engster
2012-11-14  1:17 ` Stefan Monnier
2012-11-14 18:56   ` David Engster
2012-11-14 21:16     ` Stefan Monnier [this message]
2012-11-15 19:51       ` David Engster
2012-11-16 13:57         ` Stefan Monnier

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=jwv1ufv28mg.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

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

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).