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: Tue, 13 Nov 2012 20:17:10 -0500	[thread overview]
Message-ID: <jwvhaot9ea4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k3tprzss.fsf@engster.org> (David Engster's message of "Tue, 13 Nov 2012 21:52:19 +0100")

> --- lisp/cedet/semantic/fw.el	2012-10-07 12:07:12 +0000
> +++ lisp/cedet/semantic/fw.el	2012-10-27 19:55:04 +0000
> @@ -421,14 +421,7 @@
>  	 ;; Don't prompt to insert a template if we visit an empty file
>  	 (auto-insert nil)
>  	 ;; We don't want emacs to query about unsafe local variables
> -	 (enable-local-variables
> -	  (if (featurep 'xemacs)
> -	      ;; XEmacs only has nil as an option?
> -	      nil
> -	    ;; Emacs 23 has the spiffy :safe option, nil otherwise.
> -	    (if (>= emacs-major-version 22)
> -		nil
> -	      :safe)))
> +	 (enable-local-variables :safe)
>  	 ;; ... or eval variables
>  	 (enable-local-eval nil)
>  	 )

Fine.

> === modified file 'lisp/cedet/semantic/symref/list.el'
> --- lisp/cedet/semantic/symref/list.el	2012-09-02 18:37:45 +0000
> +++ lisp/cedet/semantic/symref/list.el	2012-11-04 21:03:27 +0000
> @@ -69,7 +69,7 @@
>  references are organized by file and the name of the function
>  they are used in.
>  Display the references in `semantic-symref-results-mode'."
> -  (interactive (list (semantic-tag-name (semantic-complete-read-tag-buffer-deep
> +  (interactive (list (semantic-tag-name (semantic-complete-read-tag-project
>  					 "Symrefs for: "))))
>    (semantic-fetch-tags)
>    (let ((res nil)

From what you say, it's OK.

> === modified file 'lisp/cedet/semantic/complete.el'
> --- lisp/cedet/semantic/complete.el	2012-10-12 19:56:34 +0000
> +++ lisp/cedet/semantic/complete.el	2012-11-04 21:06:33 +0000
> @@ -1340,7 +1343,10 @@
 
>  (defmethod semantic-displayor-scroll-request ((obj semantic-displayor-abstract))
>    "A request to for the displayor to scroll the completion list (if needed)."
> -  (scroll-other-window))
> +  (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.

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


        Stefan



  reply	other threads:[~2012-11-14  1:17 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 [this message]
2012-11-14 18:56   ` David Engster
2012-11-14 21:16     ` Stefan Monnier
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=jwvhaot9ea4.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).