emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien <bzg@altern.org>, Org Mode <emacs-orgmode@gnu.org>,
	Nicolas Goaziou <n.goaziou@gmail.com>,
	Marcelo de Moraes Serpa <celoserpa@gmail.com>
Subject: Re: Move to item to the bottom
Date: Fri, 01 Jul 2011 11:14:46 +0100	[thread overview]
Message-ID: <871uyapasp.fsf@ucl.ac.uk> (raw)
In-Reply-To: <4BFA361F-7DED-4A0E-9C13-DB2EE29AA95B@gmail.com> (Carsten Dominik's message of "Fri, 1 Jul 2011 11:34:57 +0200")

Carsten Dominik <carsten.dominik@gmail.com> writes:

> On Jul 1, 2011, at 10:57 AM, Bastien wrote:
>
>> Hi Nicolas,
>> 
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>> 
>>> Correcting myself, I paste here another try to the problem at
>>> hand. Indeed, moving an item to a list he doesn't directly belong to
>>> makes little sense. Thus, the item will be moved at the end of its
>>> list.
>> 
>> Nice.  Such a move could be bound to M-<up> when the cursor is on the
>> first item, instead of throwing an error, as it does now.
>> 
>> What do you think?
>
> This does sound counter-intuitive to me.
>
> - Carsten
>

I agree but there *is* some precedence for this type of behaviour in
Emacs: e.g. the bs buffer display package where moving up (<up>) at the
top of the list of buffers takes you to the bottom of the list and vice
versa (<down>)?

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.533.gdffdb)

  parent reply	other threads:[~2011-07-01 10:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 16:13 Move to item to the bottom Marcelo de Moraes Serpa
2011-06-30 18:55 ` Nicolas Goaziou
2011-07-01  6:35   ` Nicolas Goaziou
2011-07-01  8:57     ` Bastien
2011-07-01  9:10       ` Nicolas Goaziou
2011-07-01  9:32         ` Bastien
2011-07-02 19:25           ` Nicolas Goaziou
2011-07-03  2:02             ` Marcelo de Moraes Serpa
2011-07-03  9:39               ` Nicolas Goaziou
2011-07-05  3:27                 ` Marcelo de Moraes Serpa
2011-07-07 15:51                   ` Marcelo de Moraes Serpa
2011-07-20 16:05                     ` Marcelo de Moraes Serpa
2011-07-27 11:22                       ` Bastien
2011-07-27 23:12                         ` Marcelo de Moraes Serpa
2011-07-01  9:34       ` Carsten Dominik
2011-07-01  9:46         ` Bastien
2011-07-01 10:25           ` Carsten Dominik
2011-07-01 16:07             ` Bastien
2011-07-01 16:59               ` Marcelo de Moraes Serpa
2011-07-01 19:25                 ` Nicolas Goaziou
2011-07-01 22:58                   ` Marcelo de Moraes Serpa
2011-07-02  8:05                     ` Nicolas Goaziou
2011-07-02  9:06                       ` Bastien
2011-07-01 10:14         ` Eric S Fraga [this message]
2011-07-01 10:27           ` Carsten Dominik

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871uyapasp.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=bzg@altern.org \
    --cc=carsten.dominik@gmail.com \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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/org-mode.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).