Re: [PATCH] ob-java

2020-11-06 Thread ian martins
I'm sorry that happened. It must have been frustrating. If you executed a
code block and no result was added to the buffer, then there's a chance it
is fixed.

Let me know how it goes.

On Fri, Nov 6, 2020 at 12:21 AM Jarmo Hurri  wrote:

>
> Hello Ian.
>
> ian martins  writes:
>
> >> Being a heavy user, I wonder if worg documentation page is being kept
> >> up to date with the changes?
> > Yes, that page is up to date. Actually, the page is new.
>
> Brilliant! So the only thing that was not up to date was me.
>
> (I wonder if it would be possible to have timestamps in worg. I have
> bumped into situations before where I have not known the temporal
> relationship between worg documentation and current org version.)
>
> > Are you using the latest?
>
> Yes.
>
> > Were there any issues when you updated?
>
> At some point I was using the latest at that time, and my org java stuff
> broke in the middle of a presentation during class. I have not had the
> time to check whether the very latest solves these issues. I will start
> preparing some new material now, and will let you know if anything weird
> happens.
>
> I greatly appreciate the effort you are putting into this package.
>
> All the best, and stay safe.
>
> Jarmo
>
>
>


Re: New bidi problems with org-mode (Arabic, Hebrew,..)

2020-11-06 Thread Samim Pezeshki
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
>
>
>
>
>


pgpMGR4uta81B.pgp
Description: PGP signature


Re: [PATCH] lisp/org.el: Use `org-document-info' face for subtitles

2020-11-06 Thread Titus von der Malsburg

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.

  Titus

>From 3d27f195a635f9ef8cbf43e1549663bef447c8fa Mon Sep 17 00:00:00 2001
From: Titus von der Malsburg 
Date: Tue, 3 Nov 2020 10:32:57 +0100
Subject: [PATCH] lisp/org.el: Display subtitle lines with document info faces

* lisp/org.el: The #+SUBTITLE: keyword is now displayed with
`org-document-info-keyword' and its value with
`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, not meta information.
---
 lisp/org-faces.el | 8 +---
 lisp/org.el   | 2 +-
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/lisp/org-faces.el b/lisp/org-faces.el
index 94b283ad6..2f3273f55 100644
--- a/lisp/org-faces.el
+++ b/lisp/org-faces.el
@@ -414,12 +414,14 @@ changes."
   'class color) (background light)) (:foreground "midnight blue"))
 (((class color) (background dark)) (:foreground "pale turquoise"))
 (t nil))
-  "Face for document date, author and email; i.e. that which
-follows a #+DATE:, #+AUTHOR: or #+EMAIL: keyword."
+  "Face for document subtitle, date, author and email; i.e. that
+which follows a #+SUBTITLE:, #+DATE:, #+AUTHOR: or #+EMAIL:
+keyword."
   :group 'org-faces)
 
 (defface org-document-info-keyword '((t :inherit shadow))
-  "Face for #+TITLE:, #+AUTHOR:, #+EMAIL: and #+DATE: keywords."
+  "Face for #+TITLE:, #+SUBTITLE:, #+AUTHOR:, #+EMAIL: and
+#+DATE: keywords."
   :group 'org-faces)
 
 (defface org-block `((t :inherit shadow
diff --git a/lisp/org.el b/lisp/org.el
index 9a13f03d6..89cb09fe1 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)))
-- 
2.25.1



Re: Bug: unsigned file `archive-contents' on orgmode.org [9.4 (9.4-19-gb1de0c-elpa @ /home/data1/protected/.emacs.d/elpa/org-20201019/)]

2020-11-06 Thread Jean Louis
* Bastien  [2020-11-05 22:59]:
> Thanks a lot, that's very useful.
> 
> Something I'm not sure: shall we sign only the "archive-contents" file
> or both "archive-contents" and "org-MMDD.tar"?
> 
> For the public key of Org ELPA, where would you expect to download it
> from? https://orgmode.org/elpa/key.asc or https://pgp.mit.edu or both?

Also packages shall be signed. So it is in GNU ELPA.

As Org mode is part of Emacs, and you as maintainer signing it, I
would personally expect it to be in ~/.emacs.d/elpa/gnupg where there
is other key from GNU ELPA. But what is best you maybe coordinate with
GNU ELPA maintainers. I think your key should be there in central GNU
ELPA and with that key it should be possible to verify orgmode.org
ELPA as well.