From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Possible bugs
Date: Sat, 10 Jun 2006 13:24:44 +0100 [thread overview]
Message-ID: <87fyidp59v.fsf@tallis.ilo.ucl.ac.uk> (raw)
Hi Dominik and all,
Thanks for org-mode. Here is a quite long list of possible bugs or
strange behavior.
* Fontification: a *bold* is not recognized as such when other than a
space or a beginning-of-line char surrounds it. Hence "(*bold*)" or
"*bold*?" are not fontified.
Additionnally: "*bold*" at the beginning of a line is also fontified
with org-level-* face. Maybe org-level-* regexps should made a space
after the "*" mandatory.
* No comment syntax is defined - "#" seems obvious.
* DEADLINE/SCHEDULED strings still matched when commented.
* The ?" char acceptable in links, which sometimes produces strange
results.
* When TYP_SEQ and TODO_SEQ both end with "TODO" (as they should do),
then `C-c a t' two redundant "DONE" options.
* Maybe links in fixed-width environments should be either expanded or
underlined (except if you got rid of every kind of fontification in
this environment).
* org-store link corrupting gnus-registry ? I'm using gnus-registry
and i did remark that org-store-link, when called on an article,
corrupted the ~/.gnus.registry.el file. I've no further hint on
*when* and *why* it happens. Seems quite random for now.
* Storing an image buffer with `org-store-link' stores the image
itself (as a read-only object). I think it would be more convenient
to have the file-name stored instead of the image.
Well... enough for today! Hope this is useful.
Best regards,
--
Bastien
next reply other threads:[~2006-06-10 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 12:24 Bastien [this message]
2006-06-10 13:16 ` Possible bugs Carsten Dominik
2006-06-10 13:45 ` Carsten Dominik
2006-06-10 16:20 ` Bastien
2006-06-10 18:59 ` Carsten Dominik
2006-06-11 11:14 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fyidp59v.fsf@tallis.ilo.ucl.ac.uk \
--to=bzg@altern.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.