emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Martin Rottensteiner <martin.rottensteiner.list@gmail.com>
To: emacs-orgmode@gnu.org
Subject: S-left / S-right with (double) prefix C-u without scheduled time (only date)
Date: Fri, 30 Oct 2020 08:16:33 +0100	[thread overview]
Message-ID: <CAE3hGsskD004omuoRvV8-gAR2BWkg3-XO4_eFLSTs84qD_1yOA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

Hi list,

i often use shift with left or right arrow keys to change the date in
org-(super-)agenda. These key combinations can be used with prefix C-u and
double prefix C-u C-u.

In my setup in org 9.4 the behaviour is like this for a scheduled date
without scheduled time (for example SCHEDULED: <2020-10-27>:
C-u S-left: Date changes to date before (26th)
C-u S-right: Date does not change
C-u C-u S-left: Date changes to date before (26th)
C-u C-u: S-right: Date does not change

I would prefer this behaviour instead (my proposal):
C-u S-left: Add a default time (e.g. 6:00)
C-u S-right: Add a default time (e.g. 6:00)
C-u C-u S-left: Add a default time (e.g. 6:00)
C-u C-u: S-right: Add a default time (e.g. 6:00)

Scheduled date+time Timestamps can afterwards be changed as expected with
C-u prefix(es).

What I found out until now:
( org-schedule nil "12:00" ) adds a time 12:00 to a SCHEDULED date property.
(if (< (length (org-entry-get nil "SCHEDULED")) 16) (print
'scheduled_time_missing) (print 'scheduled_time_existent))
org-timestamp-has-time-p: could maybe better be used instead for finding
out if time is not present.

I think this would be a better default behaviour or the current behaviour
might even be a bug.

   Thanks, Martin :)

[-- Attachment #2: Type: text/html, Size: 1689 bytes --]

             reply	other threads:[~2020-10-30 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30  7:16 Martin Rottensteiner [this message]
2020-11-03  6:22 ` S-left / S-right with (double) prefix C-u without scheduled time (only date) Kyle Meyer

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=CAE3hGsskD004omuoRvV8-gAR2BWkg3-XO4_eFLSTs84qD_1yOA@mail.gmail.com \
    --to=martin.rottensteiner.list@gmail.com \
    --cc=emacs-orgmode@gnu.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/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).