From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Schedule event
Date: Sun, 07 Aug 2011 08:12:10 +0200 [thread overview]
Message-ID: <8039hdhhs5.fsf@somewhere.org> (raw)
In-Reply-To: CAMXnza3QMW7bCY21gRXMXHpX5GBfYtsRiFNR63ViKuJYL8e_sw@mail.gmail.com
Hi Suvayu,
suvayu ali wrote:
> On Sat, Aug 6, 2011 at 8:59 PM, Sebastien Vauban wrote:
>> suvayu ali wrote:
>>> On Sat, Aug 6, 2011 at 5:00 PM, Sebastien Vauban wrote:
>>>>> Another idea would be to introduce another keyword like APPT an place
>>>>> these time stamps also into the second line. That might be more easy to
>>>>> implement.
>>>>
>>>> FWIW, my instinctive reaction would be: yes, great! Maybe that clarifies
>>>> the bits around dates: all active dates get keywords, only inactive ones
>>>> are without any keyword.
>>>
>>> Yes, this would be a nice addition. I always find it difficult to decide
>>> how to put regular timestamps too.
>>
>> By regular timestamps, you mean: inactive timestamps? Can you, maybe,
>> comment on what makes the decision difficult?
>
> I meant active timestamps. I'll give you an example of a dilemma.
>
> * Timestamp in headline <2011-08-06 Sat>
> For long headlines, this becomes really ugly.
I never used that form, in fact, because I don't like information to be placed
at different columns over the different headlines.
> * Timestamp below headline
> <2011-08-06 Sat>
>
> Problem with this is, I can't use fill paragraph otherwise it gets
> wrapped with the timestamp. The solution is to have a blank line in
> between.
Nor can't you do it with the first version, right?
And the problem will stay, even if we have events keyword'ed with APPT or
EVENT, do you agree?
I never use `M-q' on headlines, as I know they have to stay on one line,
whichever their length... A solution to this could be to make an Org-aware
version of `M-q' that would not try to refill Org headlines.
> As you see, my reasons are mostly about personal preference and
> aesthetics.
OK.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-08-07 6:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 17:05 Schedule event Jason Dunsmore
2011-08-06 6:19 ` Carsten Dominik
2011-08-06 15:00 ` Sebastien Vauban
2011-08-06 18:15 ` suvayu ali
2011-08-06 18:59 ` Sebastien Vauban
2011-08-06 19:42 ` suvayu ali
2011-08-07 6:12 ` Sebastien Vauban [this message]
2011-08-06 19:45 ` Jason Dunsmore
2011-08-07 6:14 ` Sebastien Vauban
2011-08-06 19:38 ` Jason Dunsmore
2011-08-07 22:06 ` Jason Dunsmore
2011-08-24 10:26 ` Bastien
2011-08-26 12:08 ` Greg Troxel
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=8039hdhhs5.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).