From: Eric J Haywiser <ejh1@MIT.EDU>
To: emacs-orgmode@gnu.org
Subject: org-4.20: A few observations
Date: Mon, 10 Apr 2006 13:00:54 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.62L.0604101254280.6184@mint-square.mit.edu> (raw)
* Observations from using org-4.19d & 4.20
** Problem: table creating with bracket link with font-lock enabled
1) Create a table row with links: OK
|---+----------+------|
| P | Location | Date |
|---+----------+------|
| | [[http://www.google.com][Google]] | |
2) with cursor at "x" press <TAB> to go to next row: PROBLEM
|---+----------+------|
| P | Location | Date |
|---+----------+------|
| | [[http://www.google.com][Google]] | x |
| | | |
3) alignment problem persists as row are added
|---+----------+------|
| P | Location | Date |
|---+----------+------|
| | [[http://www.google.com][Google]] | x |
| | | |
| | | |
4) Moving cursor outside table and returning then typing <TAB> does
not resolve the problem.
5) However moving outside table and typing a char, killing line,
etc. then returning and typing <TAB> fixes alignment
|---+----------+------|
| P | Location | Date |
|---+----------+------|
| | [[http://www.google.com][Google]] | x |
| | | |
| | | |
| | | |
a
6) Alignment after HTML export is correct ;)
** Problem: ispell hangs in org buffers with bracket links when font lock
is on
N.B. This is probably an old ispell. Can someone running a
newer version confirm this behavior?
ispell-version's value is
"ispell.el 3.4 -- Fri Aug 4 09:41:50 PDT 2000"
** Problem: Strange edit behavior with links
*** Kill-line behavior depends on font lock state with links in column 0
Consider the following pair of links with the cursor on the
blank line between them, executing kill-line
kills next two lines when font lock mode is on but only one line when
font lock mode is off.
[[http://www.google.com][Google]]
[[http://www.google.com][Google]]
*** Not a problem for links in column >1
[[http://www.google.com][Google]]
[[http://www.google.com][Google]]
[[http://www.google.com][Google]]
[[http://www.google.com][Google]]
** Observation: TODO sequences and dynamic setting of org-todo-keywords
I'm uncertain if this is expected or a bug, but the sequence outlined
below causes problems. I've empirically determined that the problems
can be avoided by:
1) M-x normal-mode after the setq.
2) Setting the org-todo-keywords in .emacs rather than via eval-region
3) Killing this buffer opening it again after setq
(effectively same as #2)
Can anyone explain the rationale behind #1: calling normal-mode?
If so, this may be something to put in the info files. I am also
aware that normal-mode is required after updating HTML style
specifications. However, it may be pleasing for newbies to understand the
reason. C-h f normal-mode isn't particularly illuminating in this regard.
*** Setup workflow described in info docs
(setq org-todo-keywords '("TODO" "FEEDBACK" "VERIFY" "DONE")
org-todo-interpretation 'sequence)
Mark above region and M-x eval-region
*** Verify variables
C-h v org-todo-keywords
org-todo-keywords's value is
("TODO" "FEEDBACK" "VERIFY" "DONE")
C-h v org-todo-interpretation
org-todo-interpretation's value is sequence
*** Create a TODO item
**** TODO This is a test
*** Try cycling with C-c C-t
**** FEEDBACK This is a test
*** Again: Try cycling with C-c C-t
**** TODO FEEDBACK This is a test
*** One more time: Try cycling with C-c C-t
**** FEEDBACK FEEDBACK This is a test
next reply other threads:[~2006-04-10 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 17:00 Eric J Haywiser [this message]
2006-04-10 20:34 ` org-4.20: A few observations Carsten Dominik
2006-04-10 21:36 ` Carsten Dominik
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=Pine.GSO.4.62L.0604101254280.6184@mint-square.mit.edu \
--to=ejh1@mit.edu \
--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).