unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jidanni@jidanni.org
To: cschol2112@googlemail.com
Cc: 8615@debbugs.gnu.org, cyd@stupidchicken.com, larsi@gnus.org,
	6954@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#8615: bug#6954: bug#8615: Please make sure v q removes the buffer for JPGs just like it does for other files
Date: Sat, 16 Jul 2011 07:22:17 +0800	[thread overview]
Message-ID: <871uxryvrq.fsf@jidanni.org> (raw)
In-Reply-To: <8762pqnxf9.fsf@jidanni.org>

All I am asking is for the same actions for the same keys.
I'm willing to learn the new keys, as long as they are consistent.
Currently q and z act differently, depending on if one is viewing a
image vs. non image.

Even though both I got to via a "v" in dired.

CS> Not sure though, why `q' does not switch back to the dired buffer. It
CS> seems to put the dired buffer second in the buffer list and switch to
CS> the buffer which is first in the list.

That needs to be fixed too. That started last week.





  parent reply	other threads:[~2011-07-15 23:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3mxgh6k9m.fsf@quimbies.gnus.org>
     [not found] ` <8762n3z13p.fsf@jidanni.org>
2011-07-15 21:30   ` bug#8615: Please make sure v q removes the buffer for JPGs just like it does for other files Lars Magne Ingebrigtsen
2011-07-15 22:57     ` bug#6954: " Christoph Scholtes
     [not found]       ` <8762pqnxf9.fsf@jidanni.org>
2011-07-15 23:22         ` jidanni [this message]
2011-07-15 23:35           ` bug#8615: " Christoph Scholtes
2011-07-15 23:38             ` Lars Magne Ingebrigtsen
2011-07-16  0:40               ` bug#6954: " Christoph Scholtes
2011-07-16 12:47               ` Antoine Levitt
2011-07-16 13:11     ` martin rudalics
2011-07-16 15:19       ` Christoph Scholtes
2011-07-20 15:09         ` bug#6954: " Chong Yidong
     [not found]           ` <87eidfar8r.fsf@jidanni.org>
2011-07-20 15:40             ` jidanni

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=871uxryvrq.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=6954@debbugs.gnu.org \
    --cc=8615@debbugs.gnu.org \
    --cc=cschol2112@googlemail.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).