[PATCH] ol-wl: add maildir and rss to folder types
with this commit, org-link can open maildir and rss folder.
more to read: http://wanderlust.github.io/wl-docs/wl.html#Folders~
---
contrib/lisp/ol-wl.el | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/contrib/lisp/ol-wl.el b/contrib/lisp/ol-wl.el
index 8c716ad..bf94531 100644
--- a/contrib/lisp/ol-wl.el
+++ b/contrib/lisp/ol-wl.el
@@ -104,9 +104,10 @@ googlegroups otherwise."
(defvar elmo-nntp-default-server)
(defconst org-wl-folder-types
- '(("%" . imap) ("-" . nntp) ("+" . mh) ("=" . spool)
-("$" . archive) ("&" . pop) ("@" . shimbun) ("[" . search)
-("*" . multi) ("/" . filter) ("|" . pipe) ("'" . internal))
+ '(("%" . imap) ("-" . nntp) ("+" . mh) ("." . maildir)
+("=" . spool) ("$" . archive) ("&" . pop) ("@" . shimbun)
+("rss" . rss) ("[" . search) ("*" . multi) ("/" . filter)
+("|" . pipe) ("'" . internal) )
"List of folder indicators. See Wanderlust manual, section 3.")
;; Install the link type
--
2.29.2
Re: [PATCH] lisp/org.el: Use `org-document-info' face for subtitles
Titus von der Malsburg writes:
> On 2020-11-06 Fr 07:18, Kyle Meyer wrote:
>> Titus von der Malsburg writes:
>>
>>> Subject: [PATCH] lisp/org.el: Use face org-document-info for subtitle
>>>
>>> * lisp/org.el: The value for the #+subtitle: property is now displayed
>>> with face `org-document-info' instead of `org-meta-line'.
>>>
>>> Like the title, author, e-mail, date, the subtitle is information
>>> that is displayed in the exported document.
>>
>> Makes sense to me, and I guess it was left out just because #+subtitle
>> wasn't around until v8.3.
>>
>>> ---
>>> lisp/org.el | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/lisp/org.el b/lisp/org.el
>>> index 03df139fb..27f09645b 100644
>>> --- a/lisp/org.el
>>> +++ b/lisp/org.el
>>> @@ -5307,7 +5307,7 @@ by a #."
>>> (min (point-max) end-of-endline))
>>>'(face org-block-end-line)))
>>> t))
>>> -((member dc1 '("+title:" "+author:" "+email:" "+date:"))
>>> +((member dc1 '("+title:" "+subtitle:" "+author:" "+email:" "+date:"))
>>> (org-remove-flyspell-overlays-in
>>>(match-beginning 0)
>>>(if (equal "+title:" dc1) (match-end 2) (match-end 0)))
>>
>> Please also update org-document-info-keyword's docstring.
>
> Done. I also updated the docstring for `org-document-info'. See attached
> patch.
Thanks. Applied (e2fe59683), add entries to the changelog for the
faces.
Re: Thoughts on the standardization of Org
* Daniele Nicolodi [2020-11-02 14:10]: > On 02/11/2020 10:02, TEC wrote: > > I think there are absolutely some benefits for Org users. I am > > personally interested in registering Org as an IANA MIME type. > > I don't think that registering Org as IANA MIME type will have the > consequences you hope it has. > > > What will this do? Well, for starters I'd like to be able to > > attach org > > files without the type being recognised as > > "application/vnd.lotus-organizer" 濫. > > This is not governed by the presence of an MIME type for Org, but by the > mechanism that assigns a MIME type to the file when it is attached tp a > message, and this is independent of the IANA MIME type database. > > You (most probably) already can configure your email client (or > operative system) to use "text/x-org" as the mime type for files with > extension ".org". Having a IANA MIME type, would only make using > "text/org" a bit more "right" (there is nothing that stops you from > using the "text/org" mime type without it being registered). That is right, I am using it since years in ~/.mailcap that works well for mutt email client. text/org; emacsclient %s; nametemplate=%s.org; text/x-org; emacsclient %s; nametemplate=%s.org; Jean
Re: New bidi problems with org-mode (Arabic, Hebrew,..)
The attached screenshot is how I see the file you sent on my screen using emacs -q I see no problem in it. Please correct me if I am wrong. Emacs 27.1 Archlinux Regards, Samim Excerpts from Fr Ml's message of November 7, 2020 10:03 pm: > Hi Samim, > > thanks for your answer. > > I tested it again with the -q option: Still have the problem (of course if I > have in the first line: -*- bidi-paragraph-direction: nil; truncate-lines: > nil; > -*-) > > - It happens only at line breaks. I think always if a word is divided. But > also > in some other cases (the new line doesn't start with space). I don't think it > depends of the length: If I enlarge the text size it changes. > > - Yes, it happens on all levels. And it happens also bei the underscore '_' > (part3). > > As I noticed in the additional edit: It happens also on windows. > > Regards, > Frank > > P.S. I've attached the org file too with some pictures of it. > > > On 11/6/20 6:22 PM, Samim Pezeshki wrote: > > Hi, > > I have no problem. I could not reproduce the issue. I tried Persian > language only. > Can the problem be of your theme? Have you tried other themes? > Please also try reproducing this with emacs -q (load Emacs with no > configuration). > Does this happen when the line exceeds a certain number of characters? > Does this happen on all org heading levels? > > Regards, > Samim > > Excerpts from Fr Ml's message of November 3, 2020 8:01 pm: > > https://emacs.stackexchange.com/questions/61494/ > new-bidi-problems-with-org-mode-arabic-hebrew > > Hallo, > > Some time ago (maybe 3 months) I've noticed some problems with the > bidi support > (right-to-left languages) in org-mode. > > One problem I can't reproduce: The characters have then a strange > form but If I > change the text scale (larger or smaller) it becomes normal. > > The second problem I can reproduce, you can see it in the two images: > > In this image: I have the option `bidi-paragraph-direction: nil`, to > get the > right direction for Hebrew and Arabic. As you see the headline color > isn't > consistently brown. The English text don't have this problem. > > [![The color of the headline changes, gets black. The direction is > right to > left][1]][1] > > In this image without the option: Everything is ok: > [![Here it's ok, the direction is left to right][2]][2] > > In both examples my init file is empty. And I've tried many fonts. My > org > version is 9.3 and emacs version is 27.1. > > Actually, the first problem is bigger for me but I can't reproduce > it; I think > that both problems appeared a the same time. So maybe solving the > second will > solve the first one too(?) > > EDIT: I can reproduce the problem with the colors also on a Windows > machine > with latest version: emacs 27.1 and the included org 9.3. With the > older > version: emacs 26.3 and the included org-version 9.1.7 I don't have > the problem > - at least I didn't see it. > > [1]: https://i.stack.imgur.com/NVUMY.png > [2]: https://i.stack.imgur.com/emHDx.png > > > > > > > -*- bidi-paragraph-direction: nil; truncate-lines: nil; -*- * سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام ** שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום *** سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום * سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام ** שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום _سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام سلام_ _שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום שלום_ pgpcpug_LylT5.pgp Description: PGP signature
Re: [PATCH] org-table: Add mode flag to enable Calc units simplification mode
Hello, I don't think this is what is holding up review of these patches, but, I recently completed the paperwork for copyright assignment to the FSF. Cheers, Dan On 24/10/2020 17:33, Daniele Nicolodi wrote: > Hello, > > attached there are a few patches reworking the parsing of org-table > formula mode strings and introducing a new mode flag to enable Calc's > units simplification mode as discussed in a recent thread on the mailing > list. I haven't updated the documentation. I can do it once we agree > that this feature is a good idea. > > I have already submitted the patches in another thread > https://orgmode.org/list/6d8c15c2-d1b0-d913-df39-c60381cff...@grinta.net/T/#m03a426dd8476b60019dfffecb8781a2126df690f > but it seems that woof did not pick them up, thus I am re-sending them. > > Cheers, > Dan >
