[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Emacs-orgmode] Possible bugs
From: |
Bastien |
Subject: |
Re: [Emacs-orgmode] Possible bugs |
Date: |
Sat, 10 Jun 2006 17:20:27 +0100 |
User-agent: |
Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux) |
Carsten Dominik <address@hidden> writes:
> FOr the coming release I have generalized the emphasis part very much
> and allowed to configure the regular expression for emphasis matching.
Works far better for me like this. I don't see any relevant
improvement to org-emphasis-regexp-components. (BTW, I've made
org-blog to use org-emph-re instead of org-bold-re and the like.)
Trying to customize org-emphasis-alist to use strike-through
fontification, i've been manually setting this:
(setq org-emphasis-alist
'(("*" bold "<b>" "</b>")
("/" italic "<i>" "</i>")
("_" underline "<u>" "</u>")
("=" shadow "<code>" "</code>")
("+" (:strike-through t) "<code>" "</code>")))
Which works great.
But doing the same from M-x customize-variable RET org-emphasis-alist
does not work, since (:strike-through t) is not recognize here as a
face.
> This is already on my list, but takes longer because headline matching
> happens in a million places in the Org-mode code, in many different
> ways. For me personally, this is usually not a problem because I
> like to indent text under a headline
Same for me - till i needed to write the org file for org-blog ;)
>> * The ?" char acceptable in links, which sometimes produces strange
>> results.
If someone quotes a link "http://like.this" then the last `"' is
fontified as part of the link.
> You should never have both in a buffer, just one is allowed. The
> result of putting both is not well defined.
Okay. Using both was quite natural to me, and no strange behavior so
far.
> Any gnus expert around here? I have not idea why and how this might
> happen.
I'm not a Gnus expert but i'll try to track down this bug further.
I let you know.
> What is an image buffer? I buffer visiting a (for example) .jpg
> file?
Yes. IMHO org-store-link in such a buffer should only store the
*file*, without inserting the image itself in the link.
--
Bastien