unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: window.el modify current emacs23 behavior of anything.
Date: Fri, 16 Sep 2011 18:36:32 +0200	[thread overview]
Message-ID: <877h585trj.fsf@gmail.com> (raw)
In-Reply-To: <4E6FA0E6.2090003@gmx.at> (martin rudalics's message of "Tue, 13 Sep 2011 20:28:54 +0200")

martin rudalics <rudalics@gmx.at> writes:

>> point doesn't move when trying to switch to a buffer at an other
>> position than the current one, when starting with `anything-samewindow'
>> enabled.
>> This is working fine in emacs23 but not here in last trunk.
>> Would be great to have same behavior as emacs23.
>
> Hopefully behaves as in emacs23 now.  Please try again.

I could get an internet connection and pull Emacs today.
Nothing have changed, the bug is always here.
The problem is the call of `bury-buffer' in `anything-cleanup'.
`bury-buffer' called with arg works as expected (It's why it was working
in your old anything of June), but fail when called with no arg.
I need to call it with no arg to be sure anything-buffer is removed from
it's window in some other use cases (e.g a dedicated window in another
frame).

So writing something like:

(if anything-samewindow (bury-buffer anything-window) (bury-buffer))

Fix this issue but create annoyances in other cases.

The best for me would be to use:

(bury-buffer)

This works as expected in Emacs23 in all use cases.

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 



  parent reply	other threads:[~2011-09-16 16:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12  6:04 window.el modify current emacs23 behavior of anything Thierry Volpiatto
2011-09-12  6:38 ` Thierry Volpiatto
2011-09-12  7:22   ` Thierry Volpiatto
2011-09-12  7:24   ` Eli Zaretskii
2011-09-12  8:52     ` Thierry Volpiatto
2011-09-12  9:03 ` martin rudalics
2011-09-12 23:26   ` Thierry Volpiatto
2011-09-13 18:28 ` martin rudalics
2011-09-13 19:12   ` Thierry Volpiatto
2011-09-16 16:36   ` Thierry Volpiatto [this message]
2011-09-16 17:10     ` martin rudalics
2011-09-16 19:34       ` Thierry Volpiatto
2011-09-17  8:42         ` martin rudalics
2011-09-17 17:06           ` Thierry Volpiatto
2011-09-17 17:28             ` martin rudalics
2011-09-18  9:08               ` Thierry Volpiatto
2011-09-19 19:35                 ` Stefan Monnier
2011-09-20 16:07                   ` martin rudalics
2011-09-20 22:08                     ` Stefan Monnier
2011-09-21  6:34                       ` Thierry Volpiatto
2011-09-21  8:35                         ` martin rudalics
2011-09-21  8:34                       ` martin rudalics
2011-09-21 12:59                         ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2011-09-16 14:23 Dmitry Gutov

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=877h585trj.fsf@gmail.com \
    --to=thierry.volpiatto@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).