From: "Alan E. Davis" <lngndvs@gmail.com>
To: org-mode <emacs-orgmode@gnu.org>
Subject: Different behavior of elipses depends on whether file is open
Date: Thu, 12 Nov 2009 22:47:44 +0000 [thread overview]
Message-ID: <7bef1f890911121447j5185c9efi2c6478959b64f189@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1188 bytes --]
I just inserted a headline using this template:
("System" ?s "* %U %(system-name):: %?%&"
"~/org/System.Journal.org" "Incoming")
I typed a long headline, and thought "Oh, well, I'll just go to the
end of the line with my special Ctl-e (stops before elipses/tags.)
Then I hit <enter>, expecting to bypass the elipses. Had I not
been schooled in the elipses issue of org-mode, I would have
deleted the elipses, as extraneous text.
But point PASSED the elipses on the same line, to the end of the
line.
This seems wrong to me. Not sure what should happen. If I enter a
tab, <enter> at the same place would indeed pass on to the next
line.
Now, I tried it again, with several conditions: short line, long
headline, text below, no text entered beyond the headline (no
<enter> while editing the remember buffer). Now I don't get this
at all. No elipses at all.
Is this because the file is already open? How can I achieve
consistency in this behavior? I tried this. The first time I enter a
headline, this behavior is observed. The second time, again a long line,
there are no elipses.
[-- Attachment #1.2: Type: text/html, Size: 1426 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
reply other threads:[~2009-11-12 22:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7bef1f890911121447j5185c9efi2c6478959b64f189@mail.gmail.com \
--to=lngndvs@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).