emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: A visibility (ellipsis) problem with `C-c .'
Date: Sun, 05 Feb 2012 02:35:55 -0500	[thread overview]
Message-ID: <7843.1328427355@alphaville> (raw)
In-Reply-To: Message from pinard@iro.umontreal.ca (=?utf-8?Q?Fran=C3=A7ois?= Pinard) of "Sat\, 04 Feb 2012 22\:27\:49 EST." <87k442t0wa.fsf@iro.umontreal.ca>

François Pinard <pinard@iro.umontreal.ca> wrote:

> Consider a header having many sub-headers, and which is closed.  So I
> only see that header, followed by an ellipsis at the end of that line.
> On that header, command `C-c .' turns the initial star (or string
> thereof) into a dash.

I don't understand: C-c . does org-time-stamp - how/why is the initial start
turned into a dash? Where exactly is the cursor at the time? If I do C-c . at
the end of the line (the final dot of the ellipis), a timestamp is inserted in
the header. I can still TAB to unfold.

Nick

>  Now, I see an item with the same text as the
> previous header, still followed by an ellipsis at the end of that line.
> Now, TAB has no effect: it does not expand the ellipsis into the
> previous contents (the minibuffer writes "EMPTY ENTRY", which is likely
> improper)
> 
> So I have to fight a tiny bit for being able to edit the contents.  I go
> one level up, collapse then expand, and everything becomes OK.
> 
> François
> 

  reply	other threads:[~2012-02-05  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05  3:27 A visibility (ellipsis) problem with `C-c .' François Pinard
2012-02-05  7:35 ` Nick Dokos [this message]
2012-02-05 12:48   ` François Pinard
2012-02-05 14:26 ` Bernt Hansen

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=7843.1328427355@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pinard@iro.umontreal.ca \
    /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).