emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: suggestion: display of #+TITLE
Date: Thu, 18 Mar 2010 10:21:32 -0400	[thread overview]
Message-ID: <87r5nhr9qr.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <FF36789F-8897-44F0-805D-6403E8B58EE9@gmail.com> (Carsten Dominik's message of "Thu, 18 Mar 2010 07:04:51 +0100")

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

> On Mar 16, 2010, at 5:25 PM, Dan Davison wrote:
>
>> Might it be worth considering a special display for the #+title line
>> in
>> org buffers?
>>
>> Currently it is easy for the title to get buried among more technical
>> configuration lines like #+options, #+startup, #+seq_toto etc. One can
>> take the approach of leaving #+title at the top of the document, and
>> moving the other config lines elesewhere, but even so I am wondering
>> whether anyone else is attracted by the idea of providing an org-title
>> display property that would hide the #+title: component, and use an
>> appropriate face for the title text.
>>
>> In some ways, the current state gives the impression that the title is
>> something which becomes important during export, but is not really a
>> key
>> component of document when it is being viewed in emacs. For example, I
>> expect others are familiar with the experience of exporting an org
>> file
>> without a title, finding that the first heading has been used as a
>> title, and then going back to add in the title as an
>> afterthought. But a
>> title is an important part of a document, and I thought perhaps a
>> special title display would help to make the title more of a first
>> class
>> citizen in org buffers?
>
> Hi Dan,
>
> I agree.  Maybe he same should be true for DATE and AUTHOR, maybe EMAIL?
>
> Would you like to make a patch for this, introducing a new face
> and applying it to these constructs?

OK, it's on my list.

Dan

>
> - Carsten
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-03-18 14:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 16:25 suggestion: display of #+TITLE Dan Davison
2010-03-18  6:04 ` Carsten Dominik
2010-03-18 14:21   ` Dan Davison [this message]
2010-03-22  1:36     ` Dan Davison
     [not found]     ` <877hp5i1wl.fsf@stats.ox.ac.uk>
2010-03-24 14:52       ` Carsten Dominik
2010-03-24 20:22         ` Scot Becker
2010-03-26  3:34           ` Dan Davison
2010-03-27 21:34             ` Scot Becker
2010-03-28  2:52               ` Dan Davison
2010-03-28  7:36                 ` Carsten Dominik
2010-03-30  2:04                 ` Thomas S. Dye

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=87r5nhr9qr.fsf@stats.ox.ac.uk \
    --to=davison@stats.ox.ac.uk \
    --cc=carsten.dominik@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).