Re: Get Grades Done: the joys of Org's simple power

[Devin Prater]

Yeah, I was hoping to just have an HTML page or something that could be put on 
Github or just sent in an email attachment, where checking checkboxes would 
update the fraction cookie.

> On Jun 12, 2020, at 9:17 PM, Phil Regier  wrote:
> 
> Oh, my.  I would not have imagined that setting up Emacspeak could be so 
> complicated.  Was your initial thought that if you could export the 
> mechanisms in your assignment to interactive HTML (of whatever form) then you 
> could let the browsers and their various accessibility APIs (of which I 
> should confess right now I have almost no knowledge) to present that 
> interactive content in whatever way the consumer of said content has 
> requested?
> 
> I'm far from being an expert, but I've spent my share of time hacking around 
> and I think there are a variety of ways that one could embed something like 
> JavaScript (I know, not an ideal choice of languages) in a variety of ways at 
> several stages in the composition-to-export process that could render the 
> output "live" if it was sufficiently simple.  And while I'm especially bad at 
> this part, a long time ago I had limited success wrapping some 
> transformations in lisp within Org-mode and I've seen others perform similar 
> trickery with greater success.
> 
> 
> On Fri, Jun 12, 2020 at 6:22 PM Devin Prater  > wrote:
> Well, some teachers are blind, which means Emacspeak, and Spacemax does have 
> visual stuff, so Emacspeak may not work well with that. I’ll have to try Doom 
> Emacs though, maybe that’ll work better. The bigger problem though, is that 
> Emacspeak relies on speech servers, and the one for Windows hasn’t been 
> updated in… quite a while. I just want not only myself and technically 
> inclined sighted teachers to be able to access this, plus its good to have 
> accessible teaching tools no matter what, because you never know when another 
> blind person may want to use it later on.
> 
>> On Jun 12, 2020, at 6:23 PM, Phil Regier > > wrote:
>> 
>> A friend showed me Org-mode running in spacemacs a few years back, and I was 
>> pretty impressed with how well it seemed to be working, though I haven't 
>> messed with it much myself.  Especially not sure how much sugar it offers as 
>> far as sharing a particular experience with new users, but at the very least 
>> you should be able to include basic usage instructions within the Org file?
>> 
>> On Wed, Jun 10, 2020 at 9:56 PM George Mauer > > wrote:
>> You know...I believe some people have gotten emacs running in browser... You 
>> could do it by compiling it to wasm. So in theory you could create a 
>> completely in-browser emacs which is optimized primarily for org mode usage.
>> 
>> Would be kind of an awesome thing for someone to tackle as it would greatly 
>> increase the reach of org. Not easy though. Could probably be a whole thesis 
>> project.
>> 
>> Not sure how well it would work with screen readers and other accessibility 
>> tech though. That would be even more work
>> 
>> On Wed, Jun 10, 2020, 10:24 PM Russell Adams > > wrote:
>> On Wed, Jun 10, 2020 at 03:38:43PM -0500, Devin Prater wrote:
>> > Now, I do wish I could share these “self-grading” performance tests with
>> > others. I’ve tried exporting one to HTML, but the grade doesn’t seem to 
>> > update
>> > automatically like it does in Org-mode.
>> 
>> Unfortunately updating the count is performed by a hook in Org when you use 
>> C-c
>> C-c to check/uncheck a box. That information is static in the text, and 
>> static
>> in html.
>> 
>> I'm not aware of a built-in way to handle that case. Sorry.
>> 
>> --
>> Russell Adamsrlad...@adamsinfoserv.com 
>> 
>> 
>> PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/ 
>> 
>> 
>> Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>> 
> 

Bug: Export to html not working [9.3.7 (9.3.7-2-g706970-elpaplus @ /Users/gmauer/.emacs.d/elpa/develop/org-plus-contrib-20200608/)]

[George Mauer]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


I wrote the following literate-programming style org file
https://github.com/togakangaroo/daily-programmer/blob/master/get-directories/README.org

When I run org-export-dispatch on this and export it to an html file it
creates a single file which - aside from the footer - contains only a
single letter `n` as contents

Emacs  : GNU Emacs 26.3 (build 1, x86_64-apple-darwin18.2.0, NS
appkit-1671.20 Version 10.14.3 (Build 18D109))
 of 2019-09-02
Package: Org mode version 9.3.7 (9.3.7-2-g706970-elpaplus @
/Users/gmauer/.emacs.d/elpa/develop/org-plus-contrib-20200608/)

current state:
==
State could not be dumped due to the following error:

(invalid-function evil-define-key)

You should still send this bug report.

Re: Get Grades Done: the joys of Org's simple power

[Phil Regier]

Oh, my.  I would not have imagined that setting up Emacspeak could be so
complicated.  Was your initial thought that if you could export the
mechanisms in your assignment to interactive HTML (of whatever form) then
you could let the browsers and their various accessibility APIs (of which I
should confess right now I have almost no knowledge) to present that
interactive content in whatever way the consumer of said content has
requested?

I'm far from being an expert, but I've spent my share of time hacking
around and I think there are a variety of ways that one could embed
something like JavaScript (I know, not an ideal choice of languages) in a
variety of ways at several stages in the composition-to-export process that
could render the output "live" if it was sufficiently simple.  And while
I'm especially bad at this part, a long time ago I had limited success
wrapping some transformations in lisp within Org-mode and I've seen others
perform similar trickery with greater success.


On Fri, Jun 12, 2020 at 6:22 PM Devin Prater  wrote:

> Well, some teachers are blind, which means Emacspeak, and Spacemax does
> have visual stuff, so Emacspeak may not work well with that. I’ll have to
> try Doom Emacs though, maybe that’ll work better. The bigger problem
> though, is that Emacspeak relies on speech servers, and the one for Windows
> hasn’t been updated in… quite a while. I just want not only myself and
> technically inclined sighted teachers to be able to access this, plus its
> good to have accessible teaching tools no matter what, because you never
> know when another blind person may want to use it later on.
>
> On Jun 12, 2020, at 6:23 PM, Phil Regier  wrote:
>
> A friend showed me Org-mode running in spacemacs a few years back, and I
> was pretty impressed with how well it seemed to be working, though I
> haven't messed with it much myself.  Especially not sure how much sugar it
> offers as far as sharing a particular experience with new users, but at the
> very least you should be able to include basic usage instructions within
> the Org file?
>
> On Wed, Jun 10, 2020 at 9:56 PM George Mauer  wrote:
>
>> You know...I believe some people have gotten emacs running in browser...
>> You could do it by compiling it to wasm. So in theory you could create a
>> completely in-browser emacs which is optimized primarily for org mode usage.
>>
>> Would be kind of an awesome thing for someone to tackle as it would
>> greatly increase the reach of org. Not easy though. Could probably be a
>> whole thesis project.
>>
>> Not sure how well it would work with screen readers and other
>> accessibility tech though. That would be even more work
>>
>> On Wed, Jun 10, 2020, 10:24 PM Russell Adams 
>> wrote:
>>
>>> On Wed, Jun 10, 2020 at 03:38:43PM -0500, Devin Prater wrote:
>>> > Now, I do wish I could share these “self-grading” performance tests
>>> with
>>> > others. I’ve tried exporting one to HTML, but the grade doesn’t seem
>>> to update
>>> > automatically like it does in Org-mode.
>>>
>>> Unfortunately updating the count is performed by a hook in Org when you
>>> use C-c
>>> C-c to check/uncheck a box. That information is static in the text, and
>>> static
>>> in html.
>>>
>>> I'm not aware of a built-in way to handle that case. Sorry.
>>>
>>> --
>>> Russell Adamsrlad...@adamsinfoserv.com
>>>
>>> PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/
>>>
>>> Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>>>
>>>
>

Re: Get Grades Done: the joys of Org's simple power

[Devin Prater]

Well, some teachers are blind, which means Emacspeak, and Spacemax does have 
visual stuff, so Emacspeak may not work well with that. I’ll have to try Doom 
Emacs though, maybe that’ll work better. The bigger problem though, is that 
Emacspeak relies on speech servers, and the one for Windows hasn’t been updated 
in… quite a while. I just want not only myself and technically inclined sighted 
teachers to be able to access this, plus its good to have accessible teaching 
tools no matter what, because you never know when another blind person may want 
to use it later on.

> On Jun 12, 2020, at 6:23 PM, Phil Regier  wrote:
> 
> A friend showed me Org-mode running in spacemacs a few years back, and I was 
> pretty impressed with how well it seemed to be working, though I haven't 
> messed with it much myself.  Especially not sure how much sugar it offers as 
> far as sharing a particular experience with new users, but at the very least 
> you should be able to include basic usage instructions within the Org file?
> 
> On Wed, Jun 10, 2020 at 9:56 PM George Mauer  > wrote:
> You know...I believe some people have gotten emacs running in browser... You 
> could do it by compiling it to wasm. So in theory you could create a 
> completely in-browser emacs which is optimized primarily for org mode usage.
> 
> Would be kind of an awesome thing for someone to tackle as it would greatly 
> increase the reach of org. Not easy though. Could probably be a whole thesis 
> project.
> 
> Not sure how well it would work with screen readers and other accessibility 
> tech though. That would be even more work
> 
> On Wed, Jun 10, 2020, 10:24 PM Russell Adams  > wrote:
> On Wed, Jun 10, 2020 at 03:38:43PM -0500, Devin Prater wrote:
> > Now, I do wish I could share these “self-grading” performance tests with
> > others. I’ve tried exporting one to HTML, but the grade doesn’t seem to 
> > update
> > automatically like it does in Org-mode.
> 
> Unfortunately updating the count is performed by a hook in Org when you use 
> C-c
> C-c to check/uncheck a box. That information is static in the text, and static
> in html.
> 
> I'm not aware of a built-in way to handle that case. Sorry.
> 
> --
> Russell Adamsrlad...@adamsinfoserv.com
> 
> PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/ 
> 
> 
> Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
> 

Re: Get Grades Done: the joys of Org's simple power

[Phil Regier]

A friend showed me Org-mode running in spacemacs a few years back, and I
was pretty impressed with how well it seemed to be working, though I
haven't messed with it much myself.  Especially not sure how much sugar it
offers as far as sharing a particular experience with new users, but at the
very least you should be able to include basic usage instructions within
the Org file?

On Wed, Jun 10, 2020 at 9:56 PM George Mauer  wrote:

> You know...I believe some people have gotten emacs running in browser...
> You could do it by compiling it to wasm. So in theory you could create a
> completely in-browser emacs which is optimized primarily for org mode usage.
>
> Would be kind of an awesome thing for someone to tackle as it would
> greatly increase the reach of org. Not easy though. Could probably be a
> whole thesis project.
>
> Not sure how well it would work with screen readers and other
> accessibility tech though. That would be even more work
>
> On Wed, Jun 10, 2020, 10:24 PM Russell Adams 
> wrote:
>
>> On Wed, Jun 10, 2020 at 03:38:43PM -0500, Devin Prater wrote:
>> > Now, I do wish I could share these “self-grading” performance tests with
>> > others. I’ve tried exporting one to HTML, but the grade doesn’t seem to
>> update
>> > automatically like it does in Org-mode.
>>
>> Unfortunately updating the count is performed by a hook in Org when you
>> use C-c
>> C-c to check/uncheck a box. That information is static in the text, and
>> static
>> in html.
>>
>> I'm not aware of a built-in way to handle that case. Sorry.
>>
>> --
>> Russell Adamsrlad...@adamsinfoserv.com
>>
>> PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/
>>
>> Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3
>>
>>

Re: [PATCH] allow for multiline headers

[Nicolas Goaziou]

Hello,

Mario Frasca  writes:

> (org-table-to-lisp): simplify code, changing a `while' to a
> `cl-loop', remove leading `hline' symbols from result, edit
> documentation to reflect change.

Please don't. Even if it has its uses, cl-loop is a complicated
non-Lispy beast, and introducing it somewhere is seldom
a simplification.

If you think cl-loop is more efficient in this function, please provide
benchmarks. But I really hope cl-loop (or cl-do, for that matter) is not
going to sprout everywhere.

Also, the first hline is used to determine where to end the header.
A table starting with a hline has no header. Therefore, I suggest to
avoid removing hlines at the beginning of a table, we would lose
information.


Regards,

-- 
Nicolas Goaziou

Re: org-lint and org-attach DIR property

[Gustavo Barros]

Hi Nicolas,

On Fri, 12 Jun 2020 at 18:59, Nicolas Goaziou  
wrote:




I removed the warning for dir property. Thank you.



Thank you very much.

Regards,
Gustavo.

Re: org-lint and org-attach DIR property

[Nicolas Goaziou]

Hello,

Gustavo Barros  writes:

> When setting the 'DIR' property for attachments for a whole file with 
> =#+PROPERTY: DIR ...=, 'org-lint' will issue a deprecation warning and 
> recommend the use "header-args" instead.  Of course, 'org-lint' means 
> here babel blocks, but as far as I understand, setting the 'DIR' 
> property for attachments for the whole file this way is a legitimate use 
> case, and is the only way to do so for org-attach.  If this is the case, 
> the warning issued by 'org-lint' might be misleading.  I'm admittedly 
> not well acquainted with 'org-lint', but thought it worth to bring the 
> case to your attention, for your consideration.

[...]

> Then visit an Org file with following contents:
>
> #+begin_src org
> ,#+property: DIR attachments
>
> ,* entry1
>
> ,* entry2
> #+end_src

You are right. I removed the warning for dir property. Thank you.

Regards,

-- 
Nicolas Goaziou

[PATCH] Re: Export to attach directory?

[Eric Abrahamsen]

Eric Abrahamsen  writes:

> I think the last thing I'm missing before my Org set up is Absolutely
> Perfect and never needs to be tweaked again (ha!) is the ability to
> export Org files/subtrees to their relevant ATTACH directories, if any.
> It might be overkill to have a global setting for this, but I would
> love to be able to say:
>
> * Report #25 :ATTACH:
> :PROPERTIES:
> :ID:   3da327aa-b51e-444a-ae5c-95bb56d025a9
> :EXPORT_FILE_NAME: report_25
> :EXPORT_TO_ATTACH: t
> :END:

Nobody seems super excited about this but...

I went poking to see how difficult it would be to do this only using
hooks and whatnot. It seemed a bit awkward: I can munge the export file
name altogether, but there's no good way to say "use whatever file name
you would have come up with, but put the resulting file in such-and-such
directory".

Mostly it's not possible to sneak in and add/alter the PUB-DIR argument
to `org-export-output-file-name' -- that argument only seems to be used
in the publishing framework.

The attached patch to `org-export-output-file-name' has it also check
for a EXPORT_PUB_DIR property at the heading level or document level;
that would allow libraries like org-attach.el a way to get at exporting
via a hook. (Maybe EXPORT_DIRECTORY would be a better name.)

Would something along these lines be considered for inclusion?

Thanks,
Eric


diff --git a/lisp/ox.el b/lisp/ox.el
index 9cf62078a..77cafb20d 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -6417,6 +6417,20 @@ Return file name as a string."
 	  "Output file: " pub-dir nil nil nil
 	  (lambda (n) (string= extension (file-name-extension n t))
 	   extension))
+	 (pub-dir (or pub-dir
+		  (and subtreep (org-entry-get
+ nil "EXPORT_PUB_DIR" 'selective))
+		  (org-with-point-at (point-min)
+			(catch :found
+			  (let ((case-fold-search t))
+			(while (re-search-forward
+"^[ \t]*#\\+EXPORT_PUB_DIR:[ \t]+\\S-"
+nil t)
+			  (let ((element (org-element-at-point)))
+(when (eq 'keyword (org-element-type element))
+  (throw :found
+	 (org-element-property
+	  :value element))
 	 (output-file
 	  ;; Build file name.  Enforce EXTENSION over whatever user
 	  ;; may have come up with.  PUB-DIR, if defined, always has

[PATCH] allow for multiline headers

[Mario Frasca]

it misses unit tests, I need to make the collapse optional, and I need 
to hear from users what they think of it.  this patch allows me to write 
a table like the following, having a three-lines header:


|  n | data | prove, |  casi, | ratio |   prove, |    casi, |
|    |  | valore | valore |   |    media | media |
|    |  | diario | diario |   | corrente | corrente |
|+--+++---+--+--|

and this is seen as a single header line.

|  n | data | prove, valore diario | casi, valore diario | ratio | 
prove, media corrente | casi, media corrente |

|+--+--+-+---+---+--|

I find it helpful, because this way my columns stay narrower.

as it is, ¡it fails on headerless tables!

I have not yet clear what's the best approach to handling headerless 
tables, was thinking of a org-table-max-collapse-header variable, which 
you would set to the number of lines which you are maximally expecting 
to collapse into the leading header line.  Or maybe an extra option to 
org-plot, where you would state if headers need be collapsed.


or we already had ways to achieve this same thing, and I missed them all?

best regards,

MF

>From 649f46a591474afb6cef8b9d5151ff6b0bae38aa Mon Sep 17 00:00:00 2001
From: mfrasca 
Date: Fri, 12 Jun 2020 11:42:34 -0500
Subject: [PATCH] lisp/org-table.el: Allow collapsing header into single line

* lisp/org-table.el (org-table-collapse-header): new function
that collapses multiple header lines into one list.
(org-table-to-lisp): simplify code, changing a `while' to a
`cl-loop', remove leading `hline' symbols from result, edit
documentation to reflect change.

* lisp/org-plot.el (org-plot/gnuplot): use
org-table-collapse-header and trust there's no leading `hline'
symbols in lisp table.
---
 lisp/org-plot.el  |  6 ++---
 lisp/org-table.el | 59 ---
 2 files changed, 43 insertions(+), 22 deletions(-)

diff --git a/lisp/org-plot.el b/lisp/org-plot.el
index a23195d2a..662d38e54 100644
--- a/lisp/org-plot.el
+++ b/lisp/org-plot.el
@@ -289,11 +289,9 @@ line directly before or after the table."
 	(setf params (plist-put params (car pair) (cdr pair)
 ;; collect table and table information
 (let* ((data-file (make-temp-file "org-plot"))
-	   (table (org-table-to-lisp))
-	   (num-cols (length (if (eq (nth 0 table) 'hline) (nth 1 table)
-			   (nth 0 table)
+	   (table (org-table-collapse-header (org-table-to-lisp)))
+	   (num-cols (length (nth 0 table
   (run-with-idle-timer 0.1 nil #'delete-file data-file)
-  (while (eq 'hline (car table)) (setf table (cdr table)))
   (when (eq (cadr table) 'hline)
 	(setf params
 	  (plist-put params :labels (nth 0 table))) ; headers to labels
diff --git a/lisp/org-table.el b/lisp/org-table.el
index 6462b99c4..6549e178a 100644
--- a/lisp/org-table.el
+++ b/lisp/org-table.el
@@ -5433,30 +5433,53 @@ a radio table."
 (defun org-table-to-lisp ( txt)
   "Convert the table at point to a Lisp structure.
 
-The structure will be a list.  Each item is either the symbol `hline'
-for a horizontal separator line, or a list of field values as strings.
-The table is taken from the parameter TXT, or from the buffer at point."
+The returned structure is a list, where each item is either the
+symbol `hline', for a horizontal separator line, or a list of
+field values as strings.  The table is taken from the parameter
+TXT, or from the buffer at point.  Leading `hline' symbols are
+trimmed, so the first item in the result is a list"
   (if txt
   (with-temp-buffer
 (insert txt)
-(goto-char (point-min))
 (org-table-to-lisp))
 (save-excursion
   (goto-char (org-table-begin))
-  (let ((table nil))
-(while (re-search-forward "\\=[ \t]*|" nil t)
-	  (let ((row nil))
-	(if (looking-at "-")
-		(push 'hline table)
-	  (while (not (progn (skip-chars-forward " \t") (eolp)))
-		(push (buffer-substring
-		   (point)
-		   (progn (re-search-forward "[ \t]*\\(|\\|$\\)")
-			  (match-beginning 0)))
-		  row))
-	  (push (nreverse row) table)))
-	  (forward-line))
-(nreverse table)
+  (let ((table (cl-loop
+		until (not (re-search-forward "\\=[ \t]*|" nil t))
+		collect (if (looking-at "-")
+'hline
+			  (cl-loop
+   do (skip-chars-forward " \t")
+		   collect (buffer-substring
+	(point)
+	(progn (re-search-forward "[ \t]*\\(|\\|$\\)")
+			   (match-beginning 0)))
+   until (looking-at "$")))
+		do (forward-line
+	(while (equal 'hline (car table))
+  (setq table (cdr table)))
+	table
+
+(defun org-table-collapse-header (table  glue)
+  "Collapse the lines before 'hline into a single header.
+
+The given TABLE is a list of lists as returned by 

Re: Get Grades Done: the joys of Org's simple power

[Diego Zamboni]

Hi Leo,

Thanks - I had seen that one too, and couldn't figure out which one
was a fork of the other one. Both have recent activity - do you know
what are the main differences between them?

--Diego

On Fri, Jun 12, 2020 at 5:54 PM Leo Okawa Ericson
 wrote:
>
> Diego Zamboni  writes:
>
> > Hi Devin,
> >
> > Your could try https://org-web.org/ - it allows online editing of Org files
> > and a quick test shows that it supports the automatic update of checkbox
> > counts.
>
> Or you could try https://github.com/200ok-ch/organice - it is a friendly
> fork of org-web.

Re: multiple EXPORT_LATEX_HEADER lines

[Jeremie Juste]

> I am not sure I understand your question.  Sorry.
You read my mind.
>
> The snippet from the OP will collate all three LaTeX header lines into a
> single line on export, which is expected in terms of org's
> behaviour.
This is exactly what I was referring to. If the behavior of
:EXPORT_LATEX_HEADER: and :EXPORT_LATEX_HEADER:+ and all the property
keys with a (+) prefix is to collate the line then it is the expected behavior.

Then keys such as :EXPORT_LATEX_HEADER: might be misleading for the
user as he may want to use multiple line header.

One solution might be to add another suffix say :EXPORT_LATEX_HEADER++:
to generate multiple lines during the export. But I'm must quickly add that I
don't have the knowledge to do it neither to  understand the implication
of this change.

Best regards,
Jeremie

PS:
> (setq message-citation-line-format "On %A, %e %b %Y at %R, %N wrote:")
Many thanks for the info. I was also given this precious reference:
(info "(sc) What Supercite Does")

Re: New mailing list archive at https://orgmode/list/

[Eric Abrahamsen]

Eric Wong  writes:

> Eric Abrahamsen  wrote:
>> Kyle Meyer  writes:
>> 
>> > [ +cc Eric Wong, mostly to say thanks for all the work he puts into
>> >   public-inbox, which is the software behind these archives, but also so
>> >   that he can correct me if I misrepresent any capabilities of or plans
>> >   for public-inbox ]
>> 
>> Thanks for this response, Kyle (and thanks for public-inbox, Eric)!
>
> you're welcome, both :>
>
>> You wouldn't really use one backend (nnweb) to provide search support
>> for another (nntp). nnir can assign different search engines to
>> different backends -- what a "search engine" boils down to is a function
>> that accepts group search criteria, and returns groups and article
>> numbers (and optional relevance scoring) for matching messages. So if
>> public-inbox had some sort of an API that accepted a query and returned
>> the above information in some sort of easily-digestible format, it
>> wouldn't be hard to write a engine for it. Articles referenced in the
>> search results would then be retrieved via NNTP, so the article numbers
>> would need to correspond.
>
> Fwiw, I've been trying to avoid exposing NNTP article numbers in
> the HTTP endpoint in favor of Message-IDs because serial numbers
> aren't decentralization-friendly.  Of course, sometimes
> Message-IDs get reused, so public-inbox will return all messages
> which match a particular Message-ID in those rare cases.
>
> Btw, POST with the "=m" query parameter already allows search
> to return a gzipped mboxrd.
>
> And also what I just wrote about about JMAP/GraphQL in the other
> message.
>
> A read-only IMAP server is also coming with search support,
> and IMAP UIDs will be equivalent to NNTP article numbers.

Sounds like something in there is bound to work! IMAP might be best --
while it's certainly possible to do Message-ID<->article number lookups,
that will slow Gnus down further, and it's already fairly slow.

Thanks again,
Eric

Re: Get Grades Done: the joys of Org's simple power

[Leo Okawa Ericson]

Diego Zamboni  writes:

> Hi Devin,
>
> Your could try https://org-web.org/ - it allows online editing of Org files
> and a quick test shows that it supports the automatic update of checkbox
> counts.

Or you could try https://github.com/200ok-ch/organice - it is a friendly
fork of org-web.

Re: multiple EXPORT_LATEX_HEADER lines

[Eric S Fraga]

On Friday, 12 Jun 2020 at 16:47, Jeremie Juste wrote:
> Many thanks for the info. So, with respect the original post, the behavior of 
> the following
> code is to be expected?

I am not sure I understand your question.  Sorry.

The snippet from the OP will collate all three LaTeX header lines into a
single line on export, which is expected in terms of org's
behaviour.  This appears to cause problems with LaTeX, which is maybe
expected or not; I don't know what LaTeX expects when working in @
letter mode as I've seldom (if ever?) had to redefine @ variables.

> PS: The automatic time stamp of the sender when replying is a nice
> piece of technology. I guess, I have to read the gnus manual
> again. :-)

I use: 

(setq message-citation-line-format "On %A, %e %b %Y at %R, %N wrote:")

eric

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-636-gaa32f6

Re: multiple EXPORT_LATEX_HEADER lines

[Jeremie Juste]

Eric S Fraga  writes:
>
> This is a standard syntax for adding values to a property.  From the info 
> manual:
>
> If you want to add to the value of an existing property, append a ‘+’ to
> the property name.  The following results in the property ‘var’ having
> the value ‘foo=1 bar=2’.
>
>  #+PROPERTY: var  foo=1
>  #+PROPERTY: var+ bar=2

Many thanks for the info. So, with respect the original post, the behavior of 
the following
code is to be expected?

* hello
  :PROPERTIES:
  :EXPORT_LATEX_HEADER: \makeatletter
  :EXPORT_LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}} 
  :EXPORT_LATEX_HEADER+: \makeatother
  :END:

Best regards,
Jeremie

PS: The automatic time stamp of the sender when replying is a nice piece
of technology. I guess, I have to read the gnus manual again. :-)
> On Friday, 12 Jun 2020 at 14:01, Jeremie Juste wrote:

Re: Bug: Option to disable evaluation of code blocks during export [9.3.7 (9.3.7-dist @ /PATH/TO/org/install/emacs/site-lisp/org/)]

[John Ciolfi]

Hi

Perhaps, in the interactive C-c C-e mode there could be:

 [C-e] Eval code blocks:  always | never | use-eval-header-setting

where 'use-eval-header-settings' is the default and uses whatever was set by 
the current org file and emacs session. Always and never would override that.

Consider the scenario where a number of people are working on a common overall 
"book" which is constructed from many org-files. The "hardcoded" setting of 
:eval no-export header in individual blocks would mean that I cannot 
interactively enable or disable the evaluation of the blocks.

Part of my confusion was that it took a little bit to figure this out (I ended 
up debugging the lisp code to get what I wanted). I think this could be 
improved in the doc, though I do admit, I'm not entirely clear on all the ways 
to control evaluation of code blocks during export. If I were, I'd propose 
something for the org manual.

Thanks
John


From: Nicolas Goaziou 
Sent: Friday, June 12, 2020 4:51 AM
To: John Ciolfi 
Cc: emacs-orgmode@gnu.org 
Subject: Re: Bug: Option to disable evaluation of code blocks during export 
[9.3.7 (9.3.7-dist @ /PATH/TO/org/install/emacs/site-lisp/org/)]

Hello,

John Ciolfi  writes:

> It would be very nice if I could enable/disable the evaluation of code
> blocks during the export process in the interactive C-c C-e
> environment.

I'm not sold to this idea. There are already many ways to control
evaluation of Babel code, i.e., :eval header arguments in its multiple
forms, `org-export-use-babel'.

Adding one more could also add confusion.

Regards,

--
Nicolas Goaziou

org-lint and org-attach DIR property

[Gustavo Barros]

Hi All,

When setting the 'DIR' property for attachments for a whole file with 
=#+PROPERTY: DIR ...=, 'org-lint' will issue a deprecation warning and 
recommend the use "header-args" instead.  Of course, 'org-lint' means 
here babel blocks, but as far as I understand, setting the 'DIR' 
property for attachments for the whole file this way is a legitimate use 
case, and is the only way to do so for org-attach.  If this is the case, 
the warning issued by 'org-lint' might be misleading.  I'm admittedly 
not well acquainted with 'org-lint', but thought it worth to bring the 
case to your attention, for your consideration.


To generate such a warning, starting with =emacs -Q=, set load-path to 
get the proper version of Org (as your case may be):


#+begin_src emacs-lisp
(add-to-list 'load-path "~/.emacs.d/elpa/org-plus-contrib-20200608")
#+end_src

Then visit an Org file with following contents:

#+begin_src org
,#+property: DIR attachments

,* entry1

,* entry2
#+end_src

'org-lint' will return:

#+begin_example
1 low   Deprecated syntax for "DIR".  Use header-args instead
#+end_example

This was tested with "Org mode version 9.3.7 (9.3.7-2-g706970-elpaplus @ 
/home/gustavo/.emacs.d/elpa/org-plus-contrib-20200608/)" and "GNU Emacs 
27.0.91 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30, cairo 
version 1.15.10) of 2020-05-20".


Best,
Gustavo.

Re: multiple EXPORT_LATEX_HEADER lines

[Eric S Fraga]

On Friday, 12 Jun 2020 at 14:01, Jeremie Juste wrote:
> But I have some more questions. I can see the :EXPORT_LATEX_HEADER in
> the properties menu. (C-x p) but how did you even find :EXPORT_LATEX_HEADER+
> property name?

This is a standard syntax for adding values to a property.  From the info 
manual:

If you want to add to the value of an existing property, append a ‘+’ to
the property name.  The following results in the property ‘var’ having
the value ‘foo=1 bar=2’.

 #+PROPERTY: var  foo=1
 #+PROPERTY: var+ bar=2

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.3.7-636-gaa32f6

Re: multiple EXPORT_LATEX_HEADER lines

[Jeremie Juste]

Hello,

can reproduce the issue with

* hello
  :PROPERTIES:
  :EXPORT_LATEX_HEADER: \makeatletter
  :EXPORT_LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}} 
  :EXPORT_LATEX_HEADER+: \makeatother
  :END:

But I have some more questions. I can see the :EXPORT_LATEX_HEADER in
the properties menu. (C-x p) but how did you even find :EXPORT_LATEX_HEADER+
property name?

I didn't see anything regarding this in the doc. It might well be
because I'm lagging behind - Org mode version 9.2.3.


Best regards,
Jeremie



Alan Schmitt  writes:

> Hello Dominik,
>
> On 2020-06-12 10:31, Dominik Schrempf  writes:
>
>> are you looking for, e.g.,
>>
>> #+latex_header: \addbibresource{bibliography.bib}
>> #+latex_header_extra: do some stuff
>> #+latex_header_extra: and even more
>>
>> I don't use the EXPORT keyword at the beginning, I am not sure if it is 
>> needed.
>
> To be more precise, I want to emulate
> #+LATEX_HEADER: \makeatletter
> #+LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}}
> #+LATEX_HEADER+: \makeatother
>
> (as a full file export, which yields 3 separate lines), for a subtree
> export, were the property :EXPORT_LATEX_HEADER: is used.
>
> Best,
>
> Alan

Re: Bug: Option to disable evaluation of code blocks during export [9.3.7 (9.3.7-dist @ /PATH/TO/org/install/emacs/site-lisp/org/)]

[Nicolas Goaziou]

Hello,

John Ciolfi  writes:

> It would be very nice if I could enable/disable the evaluation of code
> blocks during the export process in the interactive C-c C-e
> environment.

I'm not sold to this idea. There are already many ways to control
evaluation of Babel code, i.e., :eval header arguments in its multiple
forms, `org-export-use-babel'.

Adding one more could also add confusion.

Regards,

-- 
Nicolas Goaziou

Re: multiple EXPORT_LATEX_HEADER lines

[Alan Schmitt]

Hello Dominik,

On 2020-06-12 10:31, Dominik Schrempf  writes:

> are you looking for, e.g.,
>
> #+latex_header: \addbibresource{bibliography.bib}
> #+latex_header_extra: do some stuff
> #+latex_header_extra: and even more
>
> I don't use the EXPORT keyword at the beginning, I am not sure if it is 
> needed.

To be more precise, I want to emulate
#+LATEX_HEADER: \makeatletter
#+LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}}
#+LATEX_HEADER+: \makeatother

(as a full file export, which yields 3 separate lines), for a subtree
export, were the property :EXPORT_LATEX_HEADER: is used.

Best,

Alan


signature.asc
Description: PGP signature

Re: multiple EXPORT_LATEX_HEADER lines

[Dominik Schrempf]

Hello,

are you looking for, e.g.,

#+latex_header: \addbibresource{bibliography.bib}
#+latex_header_extra: do some stuff
#+latex_header_extra: and even more

I don't use the EXPORT keyword at the beginning, I am not sure if it is needed.

Best,
Dominik

Alan Schmitt  writes:

> Hello,
>
> I would like to have a multi-line export header when exporting a
> subtree. I tried this:
>
> :EXPORT_LATEX_HEADER: \makeatletter
> :EXPORT_LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}}
> :EXPORT_LATEX_HEADER+: \makeatother
>
> The problem is that it's exported on a single line, and as such it does
> not work. Is there a way to have the multiple properties exported as
> multiple lines, or to specify in the property there is a line break?
>
> Thanks,
>
> Alan

multiple EXPORT_LATEX_HEADER lines

[Alan Schmitt]

Hello,

I would like to have a multi-line export header when exporting a
subtree. I tried this:

:EXPORT_LATEX_HEADER: \makeatletter
:EXPORT_LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}}
:EXPORT_LATEX_HEADER+: \makeatother

The problem is that it's exported on a single line, and as such it does
not work. Is there a way to have the multiple properties exported as
multiple lines, or to specify in the property there is a line break?

Thanks,

Alan


signature.asc
Description: PGP signature