emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Daniel Clemente <n142857@gmail.com>
Cc: Rustom Mody <rustompmody@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: structure editing in brainstorming mode
Date: Wed, 31 Dec 2008 14:28:17 +0100	[thread overview]
Message-ID: <C49533D1-56F4-48FD-B400-1498FF256184@uva.nl> (raw)
In-Reply-To: <87ljtwinjz.fsf@CPU107.opentrends.net>


On Dec 31, 2008, at 12:36 PM, Daniel Clemente wrote:

>
>>> Thanks.  But I had to turn on transient mark mode for it to work.
>>> Intended behavior I guess?
>>
>> Yes.  Everybody should turn it on.  Why would you not?
>>
>
>  Why „should“ everyone use transient mark mode? Not everyone has to  
> like that setting, and some may prefer to work without it.
>
>  I myself find it confusing because when I set the mark, I want just  
> to mark that point for later use (to jump quickly there, for  
> instance). transient-mark-mode assumes that I always want to *start  
> a region*, which is not true.
>
>  I also like to select text without highlighting; it is less  
> distracting and more readable.
>
>
>  I wish you a (transient-mark-mode -1) and a happy new year :-)


OK, point taken.  I hardly ever use the mark as a jumping point.

When I need to remember a position, most of the time I split the
window, go to where I want momentarily in the new window, and
then close that window again.

I thought that transient-mark-mode was the only way to make use
of commands that automatically use the region if one is active.
But because of your mail, I went back to the Emacs manual and
learned about the Momentary Mark, which is
transient-transient-mark-mode, sort of.  Pretty nice, this is
a viable alternative to turning on transient-mark-mode, so viable
that I am now considering turning off transient-mark-mode :-)

OK, rephrase:

   To use region-sensitive commands, everybody should either
   turn on transient-mark-mode, or learn about the momentary mark.


May your transition into the next year be highlighted.

- Carsten



>
> Daniel

  reply	other threads:[~2008-12-31 13:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-29  5:58 Rustom Mody
2008-12-29 12:51 ` Matthew Lundin
2008-12-30 23:55   ` Carsten Dominik
2008-12-31  6:04     ` Rustom Mody
2008-12-31  8:07       ` Carsten Dominik
2008-12-31 11:36         ` Daniel Clemente
2008-12-31 13:28           ` Carsten Dominik [this message]
2008-12-31 13:33             ` Daniel Martins
2009-01-01  6:42             ` Rustom Mody
2009-01-01  8:58               ` Carsten Dominik
2009-01-01 22:53         ` Matthew Lundin
2008-12-29 16:36 ` Bernt Hansen
2008-12-29 17:15   ` Nick Dokos
2008-12-30  0:50 ` Olaf Dietsche
2008-12-30 14:11   ` Rustom Mody
2008-12-31  0:23     ` Carsten Dominik
     [not found] <200812291702.mBTH2sVD004384@bp34.u.washington.edu>
2008-12-29 19:44 ` Scott Otterson
2008-12-29 20:10   ` Matthew Lundin

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=C49533D1-56F4-48FD-B400-1498FF256184@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=n142857@gmail.com \
    --cc=rustompmody@gmail.com \
    --subject='Re: structure editing in brainstorming mode' \
    /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

Code repositories for project(s) associated with this 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).