[ANN] icsorg - node script to import events into org

[Tim Cross]

Hi All,

I've written a simple node script which imports events from an .ics file
into org, allowing them to show up in your agenda. This is based on
ideas discussed in
https://orgmode.org/worg/org-tutorials/org-google-sync.html. It is
effectively a Javascript version of the ics2org Awk script, but with the
additional capability of being able to automatically download the .ics
file from Google.

Prerequisites for the script are a fairly recent node version (at least
v12) and NPM. The script has only been tested on Linux, but hsould work
fine on macOS. Windows is an unknown quantity.

The homepage is https://github.com/theophilusx/icsorg

You can install the script by running

npm i -g icsorg

You can then run

icsorg -h

to see some usage information. Check the package README or the homepage
for more details.

Re: Help requested: Support for basic Org mode support in tools outside of Emacs

[Bo Grimes]

On 8/6/21 10:00 AM, Karl Voit wrote:

* M  ‘quintus’ Gülker  wrote:

The problem with the approach you describe in this article is that the
org markup is not really separatable from org as a part of Emacs.


This is absolutely true and I'm going to try something to change
that in the upcoming months. ;-)




I'm not competent to decide, but it looks to me like the Sublime Text 
plugin  goes a long way towards 
this change.


--
Bo Grimes

Re: [PATCH] org-agenda.el: Avoid dependency on subr-x

[Timothy]

Hi Maxim,

> Timothy, I have seen that discussion. For me it does not matter in which way
> org-agenda.el will be fixed: by adding (require ’subr-x) or by using string=
> instead of string-empty-p. Both variants work with Emacs-26.3. The point is 
> that
> “make single” should work without warnings and in the case of mixed install
> users should not get confusing errors that resemble real issues.
>
> The only reason why I suggested namely to avoid string-empty-p is that
> compatibility with Emacs-24.3 is still declared in Org sources.

Ah, cool. I took your original email to indicate that this change was solely for
Emacs 24.3 comparability, but I now see you simply used that as a reason to
choose between two different fixes.

All the best,
Timothy

Re: Number format for table results outut from R data.frame/tibble

[Berry, Charles]

John,

> On Aug 6, 2021, at 8:38 AM, John Hendy  wrote:
> 
> Greetings,
> 
> I'm wondering how to align the results from the R buffer (which I
> like) vs. the results printed by Org-mode for table results. Here's a
> toy example:
> 

`tbl_df' objects come with their own print/show method. And it does things like 
add color and text formats. This is nice in a terminal, but not when you want 
to display them in org.

Turning off the color might be enough to give you a usable result:

#+begin_src R :session foo :results output drawer
library(tibble)
options( cli.num_colors=1 )
tmp <- tibble(x=1:5, y=x/pi)
tmp
#+end_src

#+RESULTS:
:results:

# A tibble: 5 x 2
  x y
   
1 1   0.3
2 2   0.6
3 3   1. 
4 4   1. 
5 5   2.
:end:


If this is not close to what you need, I suggest writing your own formatting 
function. If you have limited emacs-lisp skill, I suggest doing this in R.

HTH,

Chuck

Re: Recursive publish bug?

[Felix E. Klee]

After a recent system update, I cannot replicate the issue anymore. 

Re: Org-cite follow function for ebib

[Thomas S. Dye]

Yes, I have set the basic follow processor and org-open-at-point takes
me to the .bib file at the entry for the key at point.

Surprisingly (to me), M-x ebib sometimes displays the entry for the key
at point, too.

All the best,
Tom

Bruce D'Arcus  writes:

> On Fri, Aug 6, 2021 at 12:47 PM Thomas S. Dye  wrote:
>>
>> Aloha Bruce,
>>
>> So, I tried calling ebib() with point on a key and it works in some
>> instances but not in others.
>
> Just to make sure I'm being clear, I mean this in your config:
>
> (setq org-cite-follow-processor 'basic)
>
> ... and then, when point is on citation and/or key:
>
> M-x org-open-at-point
>
> ... which is what calls the follow processor.
>
> If that doesn't work, you can probably look at the oc-basic code and
> see how to adapt it for ebib.
>
> Bruce


--
Thomas S. Dye
https://tsdye.online/tsdye

Re: [PATCH] org-agenda.el: Avoid dependency on subr-x

[Maxim Nikulin]

On 05/08/2021 19:59, Timothy wrote:



Restore compatibility with Emacs-24.3.


FYI Emacs 24 is no longer Org’s minimum version, from the next release onward
it will be Emacs 25.


Timothy, I have seen that discussion. For me it does not matter in which 
way org-agenda.el will be fixed: by adding (require 'subr-x) or by using 
string= instead of string-empty-p. Both variants work with Emacs-26.3. 
The point is that "make single" should work without warnings and in the 
case of mixed install users should not get confusing errors that 
resemble real issues.


The only reason why I suggested namely to avoid string-empty-p is that 
compatibility with Emacs-24.3 is still declared in Org sources.

Re: Org-cite follow function for ebib

[Bruce D'Arcus]

On Fri, Aug 6, 2021 at 12:47 PM Thomas S. Dye  wrote:
>
> Aloha Bruce,
>
> So, I tried calling ebib() with point on a key and it works in some
> instances but not in others.

Just to make sure I'm being clear, I mean this in your config:

(setq org-cite-follow-processor 'basic)

... and then, when point is on citation and/or key:

M-x org-open-at-point

... which is what calls the follow processor.

If that doesn't work, you can probably look at the oc-basic code and
see how to adapt it for ebib.

Bruce

Re: Org-cite follow function for ebib

[Thomas S. Dye]

Aloha Bruce,

So, I tried calling ebib() with point on a key and it works in some
instances but not in others.

So far, it works sometimes on plain cite: keys, but never on styles or
variants, like cite/a/f:

It would be magical if something this simple would do the trick.

All the best,
Tom

Bruce D'Arcus  writes:

> On Fri, Aug 6, 2021 at 11:50 AM Thomas S. Dye  wrote:
>>
>> Aloha Eric,
>>
>> That function opens a window on the ebib database and displays the
>> record with the key at point.
>
> So does the oc-basic follow function not provide this?
>
> I guess I'm unclear if one can configure ebib to open bib files by
> default. If yes, I would think oc-basic would be sufficient.
>
> If not, FWIW, org-ref-cite-follow is extensible via hydra+ (as is
> bibtex-actions-follow via a custom embark keymap).
>
> Depends if you want just a single function to run, or you want a menu
> of choices.
>
> Bruce


--
Thomas S. Dye
https://tsdye.online/tsdye

Re: Org-cite follow function for ebib

[Bruce D'Arcus]

On Fri, Aug 6, 2021 at 11:50 AM Thomas S. Dye  wrote:
>
> Aloha Eric,
>
> That function opens a window on the ebib database and displays the
> record with the key at point.

So does the oc-basic follow function not provide this?

I guess I'm unclear if one can configure ebib to open bib files by
default. If yes, I would think oc-basic would be sufficient.

If not, FWIW, org-ref-cite-follow is extensible via hydra+ (as is
bibtex-actions-follow via a custom embark keymap).

Depends if you want just a single function to run, or you want a menu
of choices.

Bruce

Re: Org-cite follow function for ebib

[Thomas S. Dye]

Aloha Eric,

That function opens a window on the ebib database and displays the
record with the key at point.

At this point, I'm just checking to see if someone has a similar
function working for the new org-cite framework.

I do appreciate the pointers to functions that do something similar
outside ebib.  They'll be useful if I try to write a function myself.

All the best,
Tom

Eric S Fraga  writes:

> On Thursday,  5 Aug 2021 at 10:12, Thomas S. Dye wrote:
>> I want to open the bib entry, something similar to org-ebib-open,
>> which works on Org mode links.
>
> Tom,
>
> maybe clarify what org-ebib-open does?
>
> For me, org-open-at-point, bound to C-c C-o, on a [cite:@key] entry,
> will open the bibliography file and place me at the correct entry.  What
> is it you want to do beyond this?
>
> (I have not used ebib in years and have forgotten what it is it might
> do.)


--
Thomas S. Dye
https://tsdye.online/tsdye

Number format for table results outut from R data.frame/tibble

[John Hendy]

Greetings,

I'm wondering how to align the results from the R buffer (which I
like) vs. the results printed by Org-mode for table results. Here's a
toy example:

#+begin_src R :session foo :output results :type table :results value
library(tibble)

tmp <- tibble(x=1:5, y=x/pi)
tmp
#+end_src

In org, I get this:

#+RESULTS:
| 1 | 0.318309886183791 |
| 2 | 0.636619772367581 |
| 3 | 0.954929658551372 |
| 4 |  1.27323954473516 |
| 5 |  1.59154943091895 |

In the buffer, I get this:
  x y
   
1 1 0.318
2 2 0.637
3 3 0.955
4 4 1.27
5 5 1.59

>From the tibble side, R points one to the pillar package[1], which
indeed affects the output in the buffer, but not in the Org results.

#+begin_src R :session foo :output results :type table :results value
library(tibble)
library(pillar)

options(pillar.sigfig=1)
tmp <- tibble(x=1:5, y=x/pi)
tmp
#+end_src

# A tibble: 5 × 2
  x y
   
1 1   0.3
2 2   0.6
3 3   1.
4 4   1.
5 5   2.

The last example here touches on accomplish this[2]... but is the only
method to write an elisp block that post-process my R results? It
seems so enticing that R can output the correct format... can Org
latch onto the exact output somehow?

I also discovered the round_df package[3], so I could bring that into
the mix and round flexibly, it seems. I don't *really* want to round,
though, I just want more digestible output.

Many thanks for any pointers, I'm suspecting the answer is before my
eyes, but I haven't figured out the proper incantation of :results,
:type, :wrap, etc...


Best regards,
John


[1] https://pillar.r-lib.org/articles/digits.html
[2] https://orgmode.org/manual/Results-of-Evaluation.html
[3] https://rdrr.io/cran/forestmangr/man/round_df.html

Re: ConTeXt exporter for Org Mode

[Jason Ross]

> There are two minor issues:
>
> - ox-context does not honour #+options: toc: nil  or too: 1
>Since it is possible to add chapter TOCs later,
>it might be a good idea to omit the main TOC or limit it to one level.

This is an excellent catch. Not sure how this slipped by over the months
but I will fix this ASAP.


> - I couldn’t find a way to change the paper size.
>There is
>  ;; US letter paper
>  ("paper-letter" . "\\setuppapersize[letter]")
>in the code, but it doesn’t appear in the output, and I prefer the 
a-sizes (especially 2 x a5 on a4)


To set the paper size in a particular document, add the following to the
document header:

#+CONTEXT_HEADER: \setuppapersize[A4]

The following code will create a "Snippet" for a4 paper size:

(add-to-list
 'org-context-snippets-alist
 '("paper-a4" . "\\setuppapersize[A4]")
 t)

You can then add the setup command to a document with the following:

#+CONTEXT_SNIPPETS: paper-a4

The following will change the settings for the article template:

(let ((article-preset
   (cdr (assoc "article" org-context-presets-alist
  (plist-put article-preset :snippets
 (cons "paper-a4" (plist-get article-preset :snippets


Alternatively, the article template can be modified without declaring
a snippet first with the following:

(let ((article-preset
   (cdr (assoc "article" org-context-presets-alist
  (plist-put article-preset :literal
 (concat (plist-get article-preset :literal)
 "\n\\setuppapersize[A4]")))

> Do you prefer to receive comments here or should I use the githup 
tracker in the future?


Specific bugs like the table of contents setting probably belong in the
github tracker. General questions like "how do I change to A4 paper"
could go either way.


Thank you for the feedback!

Jason

Re: Help requested: Support for basic Org mode support in tools outside of Emacs

[Karl Voit]

* M  ‘quintus’ Gülker  wrote:
> Am 04. August 2021 um 12:57 Uhr +0200 schrieb Karl Voit:
>> My focus is on Emacs-independent tools, emphasizing the argument
>> that Org mode is not Emacs-only and its syntax does have
>> applications outside of Emacs as well because it is a well-defined
>> syntax in the sense of
>> https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
>
> It is an interesting post, thank you for sharing. Indeed, a list of
> non-Emacs org tools would benefit org's popularity as a markup
> language. Good luck with building one!
>
> The problem with the approach you describe in this article is that the
> org markup is not really separatable from org as a part of Emacs.

This is absolutely true and I'm going to try something to change
that in the upcoming months. ;-)

-- 
get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <
Personal Information Management > http://Karl-Voit.at/tags/pim/
Emacs-related > http://Karl-Voit.at/tags/emacs/

"Continuous Integration and TeX with Org-Mode", by Rohit Goswani (TUG 2021)

[Juan Manuel Macías]

Hi all,

I share here the announcement of this presentation by Rohit Goswani
entitled "Continuous Integration and TeX with Org-Mode", scheduled for
Saturday, 7 Aug, within TUG 2021:


Sat, 7 Aug – 10:30 AM | Rohit Goswami Continuous Integration and TeX
with Org-Mode

In this talk I would like to introduce the usage of TeX and templates
along with generating ad-hoc class and style files for working with
orgmode. In particular, I will highlight also the process by which
literate programming practices can be implemented with babel. This
allows for a more native and flexible alternative to vendor locked in
systems like Jupyterlab which rely on JS based inelegant approaches
towards TeX typesetting. Alternative pdf generating backends consuming
TeX like Sphinx will also be covered. Finally, I would like to go into
how to leverage CI methods for TeX workflows augmented with git.
---

More info: https://tug.org/tug2021/sched.html

Best regards,

Juan Manuel 

Re: ConTeXt exporter for Org Mode

[Axel Kielhorn]

> Am 04.08.2021 um 18:01 schrieb Jason Ross :
> 
> Hello,
> 
> I have developed a ConTeXt exporter for Org Mode. It is available at
> https://github.com/Jason-S-Ross/ox-context
> 
> The exporter provides custom environments for each document element
> in an effort to make customization easier, in contrast to the Pandoc
> exporter which uses built-in environments for document elements.
> 
> I welcome any feedback.

This is great news since I’m moving to ConTeXt for new documents.)
Thanks for your work.

I tried it on some small documents and it worked great.

There are two minor issues:

- ox-context does not honour #+options: toc: nil  or too: 1 
  Since it is possible to add chapter TOCs later, 
  it might be a good idea to omit the main TOC or limit it to one level.

- I couldn’t find a way to change the paper size.
  There is 
;; US letter paper
("paper-letter" . "\\setuppapersize[letter]")
  in the code, but it doesn’t appear in the output, and I prefer the a-sizes 
(especially 2 x a5 on a4)

Do you prefer to receive comments here or should I use the githup tracker in 
the future?

Greetings
Axel




ECM1.org
Description: Binary data

Re: Org-cite follow function for ebib

[Eric S Fraga]

On Thursday,  5 Aug 2021 at 10:12, Thomas S. Dye wrote:
> I want to open the bib entry, something similar to org-ebib-open,
> which works on Org mode links.

Tom,

maybe clarify what org-ebib-open does?

For me, org-open-at-point, bound to C-c C-o, on a [cite:@key] entry,
will open the bibliography file and place me at the correct entry.  What
is it you want to do beyond this?

(I have not used ebib in years and have forgotten what it is it might
do.)

-- 
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-607-g185706
: Latest paper written in org: https://arxiv.org/abs/2106.05096