emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Phil Rooke <phil@yax.org.uk>
Cc: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Custom agenda question
Date: Thu, 27 Aug 2009 10:08:03 +0200	[thread overview]
Message-ID: <3D1B7772-DE95-4B98-90E9-A975DF644325@gmail.com> (raw)
In-Reply-To: <m263casdry.fsf@bo.yax.org.uk>


On Aug 26, 2009, at 7:09 PM, Phil Rooke wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Aug 26, 2009, at 2:04 PM, Daniel Clemente wrote:
>>
>>> I saw something strange: Emacs seems to beep with each C-n on that
>>> view. Not with C-p.
>>>
>>> The following (ding) is being run on next-line due to the condition
>>> end-of-buffer, I don't know why:
>>>
>>>   (if (interactive-p)
>>> 	(condition-case nil
>>> 	    (line-move arg nil nil try-vscroll)
>>> 	  ((beginning-of-buffer end-of-buffer) (ding)))
>>>     (line-move arg nil nil try-vscroll)))
>>> nil)
>>>
>>> The call was:
>>> (line-move 1 nil nil 1)
>>
>> Interesting.  But I cannot reproduce it.
>
> I too am having the exact same (minor) problem as Daniel.  
> Additionally,
> in the 'E' expanded view the 'p' command will move to the end of the
> line containing the previous agenda entry as opposed to hugging the
> leftmost column as it does in the non-expanded view.

I cannot believe it, there really *are* people who use Emacs
and accept the new line-move-visual default value?????  This
drives me sooo crazy when editing code and other line-organized
content - which, frankly, is *all* the stuff I do edit in Emacs.
The absolute first line in my .emacs file is

(setq line-move-visual nil)

Anyway, I am now overruling this for the agenda, to get rid
of the beep for now.  I guess this should count as an Emacs
bug, though.

- Carsten

      reply	other threads:[~2009-08-27  8:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  2:44 Custom agenda question Anthony Fairchild
2009-08-19  6:34 ` Manish
2009-08-19  9:34 ` Carsten Dominik
2009-08-19  9:59   ` Manish
2009-08-23 16:57     ` Carsten Dominik
2009-08-24  0:21       ` Manish
2009-08-24 18:03         ` Carsten Dominik
2009-08-25  8:40           ` Manish
2009-08-25  8:55             ` Carsten Dominik
2009-08-25 13:57             ` Bernt Hansen
2009-08-25 16:06               ` Carsten Dominik
2009-08-26 11:12               ` Carsten Dominik
2009-08-26 11:32                 ` Bernt Hansen
2009-08-27 16:38                 ` Bernt Hansen
2009-08-28  8:44                   ` Carsten Dominik
2009-08-28 12:06                     ` Bernt Hansen
2009-08-28 12:18                     ` Bernt Hansen
2009-08-25 12:36           ` Peter Westlake
2009-08-26 12:04           ` Daniel Clemente
2009-08-26 12:28             ` Carsten Dominik
2009-08-26 16:11               ` Daniel Clemente
2009-08-26 17:09               ` Phil Rooke
2009-08-27  8:08                 ` Carsten Dominik [this message]

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=3D1B7772-DE95-4B98-90E9-A975DF644325@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=phil@yax.org.uk \
    /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).