Re: LaTeX tutorial (focused on what Org exports) ??

[Ihor Radchenko]

David Masterson  writes:

> "Fraga, Eric"  writes:
>
>> A couple of documents I have used in the past might be useful:
>>
>> - https://archive.org/details/lshort
>
> This one sounds interesting and it's online.

There is also LaTeX Tutorials. A primer
https://www.tug.org/twg/mactex/tutorials/ltxprimer-1.0.pdf

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: LaTeX tutorial (focused on what Org exports) ??

[David Masterson]

"Thomas S. Dye"  writes:

> David Masterson  writes:
>
>> Anyone have a recommendation for a LaTeX tutorial that would
>> (especially) help me understand the LaTeX exported by Org and how to
>> enhance what is exported (new document classes, etc.).  I don't want
>> to
>> bore you all with a lot of questions, so I'm looking for a good
>> book.
>
> Org's latex exporter is exceptionally capable.  AFAICT, it doesn't
> have practical limits on the LaTeX it produces, at least for my 
> academic use case.  I'm able to use all of the LaTeX packages I've
> ever wanted to use.
>
> With the world of LaTeX at your feet, I recommend The LaTeX Companion
> by Mittelbach and Goosens.  My well-worn copy is almost 20 years old,
> and I use it as often now as when I did all of my writing in LaTeX.
> Of course, there are many new LaTeX packages in the last 20 years, but
> LaTeX was very capable at the turn of the millennium and the few new
> packages I use were easy to discover by browsing.

Hmmm.  I'll look into it.  Thanks.

-- 
David Masterson

Re: LaTeX tutorial (focused on what Org exports) ??

[David Masterson]

"Fraga, Eric"  writes:

> A couple of documents I have used in the past might be useful:
>
> - https://archive.org/details/lshort

This one sounds interesting and it's online.

> - https://texdoc.org/serve/visualFAQ.pdf/0

I'm not sure what language this one is in.

Thanks.
-- 
David Masterson

Re: [BUG] Checkbox item is broken in html export with table content [9.6 (9.6-??-bed47b437 @ /Users/hw/.emacs.d/.local/straight/build-28.1/org/)]

[Max Nikulin]

On 31/12/2022 21:08, Ihor Radchenko wrote:

nunnery-09-bayside writes:


a. [ ] foo
b. [ ] bar

| a | b | c |


[] foo
[] bar


I would expect e.g.

[] bar


   



Probably, the reason is  tag in the first paragraph of the item.
I am not sure, however, if it is safe to drop it.


If an item contains block-level element then text paragraphs should be 
wrapped with ..., however there is no reason to put checkboxes 
outside of first paragraphs.



http://permalink.gmane.org/gmane.emacs.orgmode/89413


https://list.orgmode.org/87ppgg26wd.wl%25n142...@gmail.com/T/#u
HTML lists are including paragraphs (…)
Mon, 04 Aug 2014 11:52:34 +0700

Re: How to disable completely org-persist

[Angelo Graziosi]

> Il 30/12/2022 18:42 Colin Baxter ha scritto:
> 
>  
> > Angelo Graziosi writes:
> 
> > tomas wrote:
> >> there is now a defvar `org-element-cache-persistent'
> 
> > Ah! didn't knew that..
> 
> > Setting
> 
> > (setq org-element-cache-persistent nil)
> 
> > seems to work..
> 
> Indeed, although I'm not yet convinced that org-persist directories wont
> eventually start showing up in /tmp!

...or in ~/.cache..

Re: Is function 'org-insert-property-drawer' usable?

[General discussions about Org-mode.]

alain.coch...@unistra.fr writes:

> The manual says:
>
>You can interactively insert a drawer at point by calling
>‘org-insert-drawer’, which is bound to ‘C-c C-x d’. [...]  With a
>prefix argument, this command calls ‘org-insert-property-drawer’,
>which creates a ‘PROPERTIES’ drawer right below the current
>headline.
>
> For me,
>
>C-u C-c C-x d
>
> does insert a 'PROPERTIES' drawer, but
>
>M-x org-insert-property-drawer
>
> does not.  In fact 'M-x org-insert-p' offers no completion.  I
> generally use this kind of information to use my own key bindings, but
> here I cannot (don't know how).

According to the source code of `org-insert-drawer', I think the manual
is saying that when ARG is non-nil, the function simply calls
`org-insert-property-drawer'.  However, `org-insert-property-drawer' is
not declared interactive, so you wouldn't be able to M-x it.  You could,
however, still run it via elisp:

  M-: (org-insert-property-drawer) RET

Best,


RY

Is function 'org-insert-property-drawer' usable?

[Alain . Cochard]

The manual says:

   You can interactively insert a drawer at point by calling
   ‘org-insert-drawer’, which is bound to ‘C-c C-x d’. [...]  With a
   prefix argument, this command calls ‘org-insert-property-drawer’,
   which creates a ‘PROPERTIES’ drawer right below the current
   headline.

For me,

   C-u C-c C-x d

does insert a 'PROPERTIES' drawer, but

   M-x org-insert-property-drawer

does not.  In fact 'M-x org-insert-p' offers no completion.  I
generally use this kind of information to use my own key bindings, but
here I cannot (don't know how).

-- 
EOST (École et Observatoire des Sciences de la Terre) 
ITE (Institut Terre & Environnement) | alain.coch...@unistra.fr
5 rue René Descartes   [bureau 110]  | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France | [ slot available for rent ]

Re: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable

[Tom Gillespie]

> P.S. Considering intense discussion around the topic, what about
> reverting my commit from the release? We can then re-consider the whole
> design and apply something more elaborate later.

I was actually going to mention that in my previous
message but forgot. I think that given the potential
for disruption and our desire to do a good job on the
design of the new system I think it would make sense
to revert the commit from the release so that we don't
rush in trying to fix something under pressure without
taking the time we need to consider all the angles.

Best!
Tom

Re: search in org-sparse-tree for multiple files

[Eric Chun]

 Ihor:  "`org-occur-next-match' does not support multiple buffers.Looking at 
the docstring of `next-error-function', I am also not sure if
we need to support this there. The docstring talks only about the
current buffer."
I'm assuming "current buffer" is the buffer which I can currently type input 
into.  The current buffer is not finding next occurrence of search string by 
pressing M-g M-n.  Is this expected?
On Saturday, December 31, 2022 at 06:38:49 AM MST, Ihor Radchenko 
 wrote:  
 
 Eric Chun  writes:

> I can't seem to use the M-g M-n keys to jump to occurrences in sparse tree 
> search for second org file within same Emacs window.
> If I search first file by pressing C-c / r  RET and then search second 
> file by pressing C-c / r  RET, I'm not able to jump to occurrences in 
> that second file by pressing M-g M-n.  I get a message saying "No more 
> matches" even though there are matches.  If I close the first file buffer, 
> then I am able to use M-g M-n to jump to occurrences in the second file.
> Does anybody know what I may be missing?
> I'm using org mode version 9.6 in Emacs 28.2 on CentOS7.

`org-occur-next-match' does not support multiple buffers.
Looking at the docstring of `next-error-function', I am also not sure if
we need to support this there. The docstring talks only about the
current buffer.

What might be relevant is `next-error-find-buffer-function' - a user
customization you may want to set.

Generally, it is unclear for me how to implement multiple buffers
support for org-spare-tree. Ideas and patches welcome.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

  

[org-promote-subtree + undo] adds one star

[Alain . Cochard]

Under release_9.6-173-g24740a

I have file

#+begin_src org
,* h1
,** h2
#+end_src

I do

   M-x org-promote-subtree

on h2, which works as expected; then

   M-x undo

The file becomes

#+begin_src org
,* h1
,** * h2
#+end_src

and I have the message

   primitive-undo: Changes to be undone by function different from
   announced


-- 
EOST (École et Observatoire des Sciences de la Terre) 
ITE (Institut Terre & Environnement) | alain.coch...@unistra.fr
5 rue René Descartes   [bureau 110]  | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France | [ slot available for rent ]

Re: Babel (scheme): Evaluation errors are not shown

[Marc Nieper-Wißkirchen]

Done!

Am Sa., 31. Dez. 2022 um 14:24 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen  writes:
>
> > Please find the patch file attached to this email.
>
> Thanks!
> I will give some general comments and leave the ob-scheme changes for
> Rudolf.
>
> > Subject: [PATCH] Display evaluation errors for Scheme code blocks.
>
> If you can, please provide changelog entries explaining each change. See
> https://orgmode.org/worg/org-contribute.html#commit-messages
>
> >(let ((buf (get-buffer-create org-babel-error-buffer-name)))
> >  (with-current-buffer buf
> >(goto-char (point-max))
> >(save-excursion
> >  (unless (bolp) (insert "\n"))
> >  (insert stderr)
> > -(insert (format "[ Babel evaluation exited with code %S ]" 
> > exit-code
> > +(when exit-code
> > +  (insert (format "[ Babel evaluation exited with code %S ]" 
> > exit-code)
>
> I think it will be more consistent to do something like
>
> (if exit-code ... (insert " [ Babel evaluation exited abnormally ] "))
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 


0001-lisp-ob-scheme.el-Do-not-hide-Scheme-evaluation-erro.patch
Description: Binary data

Re: ob-shell intentions and paperwork (was Bash results broken?)

[Ihor Radchenko]

Matt  writes:

> I've backed out the `require' change and adjusted everything else based on 
> your feedback.  There is a separate patch for each refactor that created a 
> new test.   The remaining refactors are in a single patch.  I was also able 
> to resolve the issue I had with inserting the test name for the session (the 
> "yes" string in `test-ob-shell/session').  The issue with 
> `org-babel-shell-initialize' still stands but is outside the scope of these 
> patches and isn't dealt with here.

Thanks!

I can see that you still prefer to use `string-join' for Org body.
Why not a bare string? There is no particular problem with
`string-join', but the rest of the tests are all using direct string
when possible - your patch makes ob-shell stand out of common style.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Re: Problems with LaTeX export for $x\text{foo $x$}$-like construts?

[Ihor Radchenko]

Pedro Andres Aranda Gutierrez  writes:

>> This is to be expected because of how Org parser works.
>
> In my experience, this also applies for some situations while creating
> listings.
> My question is if there would be space for a `:raw t` in the
> `#+begin_export latex` to produce a _verbatim_ copy of the contents of the
> environment.

Listings should be different.
Please provide a problematic example.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] Checkbox item is broken in html export with table content [9.6 (9.6-??-bed47b437 @ /Users/hw/.emacs.d/.local/straight/build-28.1/org/)]

[Ihor Radchenko]

nunnery-09-bays...@icloud.com writes:

> The HTML Export is a bit broken when the checkbox item has table
> content. See the HTML exporting difference between section A and B in follow 
> code. (also attached a screenshot below)
>
> #+BEGIN_SRC org
> * A
> 1. [ ] test
> 2. [ ] foo
> 3. [ ] bar
>
> * B
> a. [ ] foo
> b. [ ] bar
>
>| a | b | c |
>|---+---+---|
>| 1 | 1 | 1 |
>| 2 | 2 | 2 |
> #+END_SRC

Confirmed, but my HTML-foo is not good enough to understand what is
wrong.

The HTML fragment in question is

[] foo
[] bar

  

The second item is _rendered_ with a newline when paragraph is inserted.

Probably, the reason is  tag in the first paragraph of the item.
I am not sure, however, if it is safe to drop it.

`org-html-paragraph' only drops  for first paragraph in an item that
is followed by either plain string or a sub-list:

((and (eq parent-type 'item)
   (not (org-export-get-previous-element paragraph info))
   (let ((followers (org-export-get-next-element paragraph info 2)))
 (and (not (cdr followers))
  (memq (org-element-type (car followers)) '(nil plain-list)
  ;; First paragraph in an item has no tag if it is alone or
  ;; followed, at most, by a sub-list.
  contents)

The relevant commit is 9a34a13c:

9a34a13c077f592c5528d95c155ecdf2d655937e
Author: Nicolas Goaziou 
AuthorDate: Tue Aug 26 09:51:20 2014 +0200
Commit: Nicolas Goaziou 
CommitDate: Tue Aug 26 09:55:54 2014 +0200
ox-html: Better criterion for first paragraphs in lists

* lisp/ox-html.el (org-html-paragraph): Do not wrap first paragraph in
  an item within  tags in the most simple cases.

Thanks to Daniel Clemente for suggesting it.
http://permalink.gmane.org/gmane.emacs.orgmode/89413

The diff in the commit suggests that dropping  is not desirable when
non-paragraphs are present in the list. In the above example, a table is
present.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] ob-core: add org-confirm-babel-evaluate-cell custom variable

[Ihor Radchenko]

Tom Gillespie  writes:

>> What about modifying `org-confirm-babel-evaluate' to allow these values:
>>
>> - t  : confirm header vars *and* code blocks
>> - 'code  : confirm code blocks
>> - 'vars  : confirm vars
>> - nil: don't confirm
>>
>> and set the default value to 'code, while allowing concerned users to
>> set it to `t' -- until we have a better system for evaluation query.
>>
>> WDYT?
>
> In short this is not a viable solution because there is no way
> to compose nil for embedded expressions with a function
> for blocks. We really do not want to change the function
> signature for the function to also have to accept whether
> it is a block or an embedded expression. That will break
> code for everyone.

Agree. The value of `org-confirm-babel-evaluate' can be a function. If
we do not change the function signature, there will be no way to provide
the code block vs. code cell granularity we are trying to handle.

We may, however, make `org-confirm-babel-evaluate' function value accept
an extra third argument - context ('code or 'vars). This will retain the
required flexibility without introducing an extra variable.

P.S. Considering intense discussion around the topic, what about
reverting my commit from the release? We can then re-consider the whole
design and apply something more elaborate later.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Broken numerical ordered list when exported to latex

[Ihor Radchenko]

Sharon Kimble  writes:

> I have a long-standing problem with a numerical ordered list which is broken 
> by sub-headings, and exported to latex.
>
> On looking at the org manual, the most recent one that I have, on page 12, it 
> shows something like '[@20]' which when exported shows exactly the same, and 
> hasn't continued the numerical numbering.
>
> So how can I have a continuing numerical ordered list please when exported to 
> latex?  

Could you please provide an example Org file, explain what you do to
export it, describe what you expect and what you get instead?
See https://orgmode.org/manual/Feedback.html#Feedback

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: search in org-sparse-tree for multiple files

[Ihor Radchenko]

Eric Chun  writes:

> I can't seem to use the M-g M-n keys to jump to occurrences in sparse tree 
> search for second org file within same Emacs window.
> If I search first file by pressing C-c / r  RET and then search second 
> file by pressing C-c / r  RET, I'm not able to jump to occurrences in 
> that second file by pressing M-g M-n.  I get a message saying "No more 
> matches" even though there are matches.  If I close the first file buffer, 
> then I am able to use M-g M-n to jump to occurrences in the second file.
> Does anybody know what I may be missing?
> I'm using org mode version 9.6 in Emacs 28.2 on CentOS7.

`org-occur-next-match' does not support multiple buffers.
Looking at the docstring of `next-error-function', I am also not sure if
we need to support this there. The docstring talks only about the
current buffer.

What might be relevant is `next-error-find-buffer-function' - a user
customization you may want to set.

Generally, it is unclear for me how to implement multiple buffers
support for org-spare-tree. Ideas and patches welcome.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Babel (scheme): Evaluation errors are not shown

[Ihor Radchenko]

Marc Nieper-Wißkirchen  writes:

> Please find the patch file attached to this email.

Thanks!
I will give some general comments and leave the ob-scheme changes for
Rudolf.

> Subject: [PATCH] Display evaluation errors for Scheme code blocks.

If you can, please provide changelog entries explaining each change. See
https://orgmode.org/worg/org-contribute.html#commit-messages

>(let ((buf (get-buffer-create org-babel-error-buffer-name)))
>  (with-current-buffer buf
>(goto-char (point-max))
>(save-excursion
>  (unless (bolp) (insert "\n"))
>  (insert stderr)
> -(insert (format "[ Babel evaluation exited with code %S ]" 
> exit-code
> +(when exit-code
> +  (insert (format "[ Babel evaluation exited with code %S ]" 
> exit-code)

I think it will be more consistent to do something like

(if exit-code ... (insert " [ Babel evaluation exited abnormally ] "))

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] warning message for straight-use-package [9.6 (9.6-gb2adb6 @ /Users/stephen/.emacs.d/straight/build/org/)]

[Ihor Radchenko]

Stephen Eglen  writes:

> I use straight.el for package management, and a recent package (I think
> it was todoist.el) pulled in org-mode.  This then caused the warning
> about mismatch between the org-mode in Emacs and the one from the repo.
>
> I read the *Warning* and in particular this bit:
>
> --
> 3. New Org version is loaded using straight.el package manager and
>other package depending on Org is loaded before straight triggers
>loading of the newer Org version.
>
>It is recommended to put
> (straight-use-package ’org)
>early in the config.  Ideally, right after the straight.el
> --
>
> so I copied the elisp straight into .emacs.  This then
> generated an error, because the symbol 'org had been copied across as
> ’org.  

Thanks for reporting!
Fixed on bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=62dc49509

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Babel (scheme): Evaluation errors are not shown

[Marc Nieper-Wißkirchen]

Please find the patch file attached to this email.

Thank you,

Marc

Am Sa., 31. Dez. 2022 um 13:07 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen  writes:
>
> > Please find attached a version that does not signal an Elisp user
> > error, but calls `org-babel-eval-error-notify' instead.
>
> If you can, could you please send the changes in form of a patch
> instead? It is then easier to review.
> See https://orgmode.org/worg/org-contribute.html#patches (you can just
> attach the patch to your reply).
>
> > To get rid of
> > the display of the arbitrary error code, could we modify
> > `org-babel-eval-error-notify' so that nothing is displayed about an
> > error if the error code is `nil'?
>
> Yes, we can. Feel free to make a patch, updating the docstring according
> to your changes.
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 


0001-Display-evaluation-errors-for-Scheme-code-blocks.patch
Description: Binary data

Re: ob-shell intentions and paperwork (was Bash results broken?)

[Ihor Radchenko]

Matt  writes:

>  > > +;; TODO refactor into macro.  Currently violates (elisp) Coding
>  > > +;; Conventions and is hard to debug.
>  > >  (defun org-babel-shell-initialize ()
>  > >"Define execution functions associated to shell names.
>  > 
>  > Could you please elaborate? Which particular convention does it violate?
>  > What is hard to debug?
>
> (elisp) Coding Conventions says,
>
> "• Constructs that define a function or variable should be macros, not
>  functions, and their names should start with ‘define-’.  The macro
>  should receive the name to be defined as the first argument.  That
>  will help various tools find the definition automatically.  Avoid
>  constructing the names in the macro itself, since that would
>  confuse these tools."
>
> The `org-babel-shell-initialize' function defines *all* the 
> `org-babel-execute:XXX' functions given by `org-babel-shell-names' (sh, bash, 
> zsh, etc.).

I agree that `org-babel-shell-initialize' could use a better name.

As for being a macro, there will be not much gain - the convention is
mostly designed for things like `cl-defun' aimed to be used in the code.
`org-babel-shell-initialize' is only used by `org-babel-shell-names'.

I do not have objections if it were a macro though. (But I do not see
how it would help debugging).

> Because `org-babel-shell-initialize' is a function factory, you can't easily 
> examine or modify their definitions.  `C-h f org-babel-execute:sh' jumps to 
> the top of lisp/ob-shell.el.  Changing the definition requires reevaluating 
> the definition for all the execute functions (or first changing 
> `org-babel-shell-names').

This is indeed a downside. Any better ideas?
ob-core dictates that we must have org-babel-execute:lang functions to
make things work.

> This was a problem for me when I wanted to make the session name string for 
> `test-ob-shell/session' the test name (mentioned above).  In the test, when I 
> replaced the session name string with a variable containing the string, 
> `org-babel-execute:sh' failed with a type error.  I couldn't get the variable 
> to evaluate (with backquote and comma or otherwise).  Without an explicit 
> function definition or a macro to expand, I found it hard to debug/experiment 
> with (and so left the test name as a hard coded string).

Could you please explain a bit more about the problem? I do not see how
macro would help in this situation.

> I probably don't need it and am happy to remove it.An older version of 
> the function was more complex and made sense as a separate function (or so I 
> thought).  My aim was to make the test strings easy to read so that it's 
> clearer what's being tested (i.e. not write multi-line strings on a single 
> line).  I could use concat and add "\n" to the end of each line.  Or, simply 
> write out the string-join.  Maybe there's another way to write multi-line 
> strings that I'm not aware of in Elisp, maybe something like Python's 
> triple-quote?

We write multi-line docstrings all the time without extra macros. I
recommend using paredit or similar packages to auto-escape things that
need to be escaped.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] ob-R.el: extra empty data.frame columns generated from plain lists after recent change [9.6 (release_9.6-3-ga4d38e @ /usr/share/emacs/30.0.50/lisp/org/)]

[Ihor Radchenko]

"Berry, Charles"  writes:

> So if elisp lists are to be converted to R lists, ob-R will need to know 
> whether the list came from a table to decide whether to render top level 
> elements as list elements or as data.frame rows.

This information should be available: lists are passed as Elisp lists to
ob-R; tables are passed as lists of lists.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

[WORG] Re: 0e6cdacc publish.sh: never publish the archive/ subdirectory

[Ihor Radchenko]

-(dolist (org-file (directory-files-recursively default-directory "\\.org$"))
+(dolist (org-file (directory-files-recursively
+  default-directory "\\.org$"
+  nil (lambda (n) (not (string-match-p "archive" n)

Won't it also discard all the files with word "archive" in them?
We don't have any now, but I imagine someone writing
org-archive-tips.org at some point - it will be ignored.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [MAINTENANCE] Org orphanage?

[Ihor Radchenko]

Bastien  writes:

>> 5. We can offer to move orphaned repositories to sr.ht under our control
>>and mention that we can do minimal maintenance then.
>
> I'm not sure about this.
>
> Another idea is to rename org-contrib to org-orphanage and to offer to
> add *.el files there?  This way we make it very obvious that these files
> receive minimal maintenance while allowing users to install them through
> GNU ELPA.
>
> WDYT?

I do not think that it is a good idea:

1. I am not sure how org-contrib to org-orphanage will affect ELPA
   package
2. Adding packages to org-contrib may surprise users who install
   org-contrib.
3. Most importantly, some packages have multiple files and provide a
   separate *-pkg.el file. Adding them to org-contrib will require extra
   work to make things installable.
4. How will we continue distributing the orphan packages on ELPA from
   the new source?   

I guess we may work around the above issues using git sub-modules, but I
am not sure if it is going to be easier compared to separate package
list.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Screenshots in ORG-NEWS (was: [PATCH] oc-csl: Improve LaTeX bibliography formatting)

[Ihor Radchenko]

Bastien Guerry  writes:

> Ihor Radchenko  writes:
>
>> I don't think we have an example.
>> Probably, we can create etc/org-news-images folder, set :DIR: property
>> in etc/ORG-NEWS to that folder, and then use attachments.
>
> I suggest we don't go in that direction: I'd rather keep etc/ORG-NEWS
> as a self-contained file.
>
> Can we use Worg instead for such examples?

I mostly had https://orgmode.org/Changes.html in mind here.
Considering the success of https://blog.tecosaur.com/tmio/, I was hoping
to provide some more elaborate NEWS file for users.

Of course, we need to keep text-only version whenever possible for
accessibility reasons, but some new features are really better received
when there is a screenshot or screencast attached to the news. (see
https://emacssurvey.org/results/3425413930 "What documentation do you
wish package authors would more often provide?")

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Babel (scheme): Evaluation errors are not shown

[Ihor Radchenko]

Marc Nieper-Wißkirchen  writes:

> Please find attached a version that does not signal an Elisp user
> error, but calls `org-babel-eval-error-notify' instead.

If you can, could you please send the changes in form of a patch
instead? It is then easier to review.
See https://orgmode.org/worg/org-contribute.html#patches (you can just
attach the patch to your reply).

> To get rid of
> the display of the arbitrary error code, could we modify
> `org-babel-eval-error-notify' so that nothing is displayed about an
> error if the error code is `nil'?

Yes, we can. Feel free to make a patch, updating the docstring according
to your changes.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: LaTeX tutorial (focused on what Org exports) ??

[Fraga, Eric]

A couple of documents I have used in the past might be useful:

- https://archive.org/details/lshort
- https://texdoc.org/serve/visualFAQ.pdf/0

-- 
: Eric S Fraga, with org release_9.6-124-g036cc0 in Emacs 30.0.50

Re: Babel (scheme): Evaluation errors are not shown

[Marc Nieper-Wißkirchen]

Am Sa., 31. Dez. 2022 um 11:19 Uhr schrieb Marc Nieper-Wißkirchen
:
>
> Am Sa., 31. Dez. 2022 um 11:09 Uhr schrieb Marc Nieper-Wißkirchen
> :
> >
> > Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko 
> > :
> > >
> > > Marc Nieper-Wißkirchen  writes:

[...]

> > >  It is not what we usually do in Org babel. If blocks execution
> > > fails, we display the error in separate buffer and still return the
> > > output available before error has been thrown. See `org-babel-eval' and
> > > `org-babel-eval-error-notify'.
> >
> > I will take a look.
>
> Hmmm... `org-babel-eval-error-notify' assumes that the code was
> evaluated by running an external script.  In the case of the Geiser
> interface to Scheme, the concept of an exit code does not make any
> sense.

Please find attached a version that does not signal an Elisp user
error, but calls `org-babel-eval-error-notify' instead.  To get rid of
the display of the arbitrary error code, could we modify
`org-babel-eval-error-notify' so that nothing is displayed about an
error if the error code is `nil'?


ob-scheme.el
Description: Binary data

Re: LaTeX tutorial (focused on what Org exports) ??

[Marcin Borkowski]

On 2022-12-31, at 02:18, Thomas S. Dye  wrote:

> David Masterson  writes:
>
>> Anyone have a recommendation for a LaTeX tutorial that would
>> (especially) help me understand the LaTeX exported by Org and how to
>> enhance what is exported (new document classes, etc.).  I don't want
>> to
>> bore you all with a lot of questions, so I'm looking for a good
>> book.
>
> Org's latex exporter is exceptionally capable.  AFAICT, it doesn't
> have practical limits on the LaTeX it produces, at least for my
> academic use case.  I'm able to use all of the LaTeX packages I've
> ever wanted to use.
>
> With the world of LaTeX at your feet, I recommend The LaTeX Companion
> by Mittelbach and Goosens.  My well-worn copy is almost 20 years old,
> and I use it as often now as when I did all of my writing in LaTeX.
> Of course, there are many new LaTeX packages in the last 20 years, but
> LaTeX was very capable at the turn of the millennium and the few new
> packages I use were easy to discover by browsing.

The "Not so short introduction to LaTeX" is also a pretty nice resource.

Also, I'm the coauthor of a (free as in beer, a bit less free as in
speech - CC-BY-NC) textbook on LaTeX, but it will probably be of no use
for you, since it's in Polish;-).

Best,

-- 
Marcin Borkowski
http://mbork.pl

Re: Babel (scheme): Evaluation errors are not shown

[Marc Nieper-Wißkirchen]

Am Sa., 31. Dez. 2022 um 11:09 Uhr schrieb Marc Nieper-Wißkirchen
:
>
> Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko 
> :
> >
> > Marc Nieper-Wißkirchen  writes:
> >
> > > I have been talking to jao (from geiser).  The following version of
> > > ob-scheme.el signals an error when executing Scheme code blocks.
> > > Besides two function declarations, the only change is in the function
> > > org-babel-scheme-execute-with-geiser.
> >
> > Do you mean that `org-babel-scheme-execute-with-geiser' throws Elisp
> > error?
>
> This is what it currently does; it packages the Scheme error as an
> Elisp *user* error.
>
> I chose this behavior to mimic what happens when Elisp code blocks
> produce errors.
>
> >  It is not what we usually do in Org babel. If blocks execution
> > fails, we display the error in separate buffer and still return the
> > output available before error has been thrown. See `org-babel-eval' and
> > `org-babel-eval-error-notify'.
>
> I will take a look.

Hmmm... `org-babel-eval-error-notify' assumes that the code was
evaluated by running an external script.  In the case of the Geiser
interface to Scheme, the concept of an exit code does not make any
sense.

Re: Babel (scheme): Evaluation errors are not shown

[Marc Nieper-Wißkirchen]

Am Sa., 31. Dez. 2022 um 10:49 Uhr schrieb Ihor Radchenko :
>
> Marc Nieper-Wißkirchen  writes:
>
> > I have been talking to jao (from geiser).  The following version of
> > ob-scheme.el signals an error when executing Scheme code blocks.
> > Besides two function declarations, the only change is in the function
> > org-babel-scheme-execute-with-geiser.
>
> Do you mean that `org-babel-scheme-execute-with-geiser' throws Elisp
> error?

This is what it currently does; it packages the Scheme error as an
Elisp *user* error.

I chose this behavior to mimic what happens when Elisp code blocks
produce errors.

>  It is not what we usually do in Org babel. If blocks execution
> fails, we display the error in separate buffer and still return the
> output available before error has been thrown. See `org-babel-eval' and
> `org-babel-eval-error-notify'.

I will take a look.

Thanks,

Marc

>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 

Re: Babel (scheme): Evaluation errors are not shown

[Ihor Radchenko]

Marc Nieper-Wißkirchen  writes:

> I have been talking to jao (from geiser).  The following version of
> ob-scheme.el signals an error when executing Scheme code blocks.
> Besides two function declarations, the only change is in the function
> org-babel-scheme-execute-with-geiser.

Do you mean that `org-babel-scheme-execute-with-geiser' throws Elisp
error? It is not what we usually do in Org babel. If blocks execution
fails, we display the error in separate buffer and still return the
output available before error has been thrown. See `org-babel-eval' and
`org-babel-eval-error-notify'.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at