Hello
There is a bug in `org-entry-get' when used with non-nil INHERIT.
When PROPERTY is set in `org-file-properties',
`org-global-properties' or `org-global-properties-fixed' then
'org-entry-get' uses that value without first checking higher
levels of the hierarchy.
-- Jonas
is resized to four lines not the document buffer.
TINYCHANGE
---
contrib/lisp/org-panel.el |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/contrib/lisp/org-panel.el b/contrib/lisp/org-panel.el
index 3ffdfaf..1df3847 100644
--- a/contrib/lisp/org-panel.el
+++ b/contr
Sorry for the corrupted commit message.
I created a patch using git-filter-branch opened the file and turned on
message-mode and hit C-c C-c - obviously that is not enough. Could
someone enlighten me how to actually submit the patches?
The commit message was supposed to look like this:
,
|
Hello
Is there a way to specify which `org-store-link-function' or link type
built into `org-store-link' should be used when there are multiple valid
types? E.g. I have loaded `org-elisp-symbol' but would still be able to
link to the library header or a "section" in the file. With
`org-store-lin
ssumed that message-mode would
either know how to correctly handle the patches/messages created by
format-patch or otherwise fail completely (instead of sending a
corrupted message).
Jonas Bernoulli (2):
Orgpan: resize the correct window
Orgpan: quiet byte-compiler
contrib/lisp/org-panel.el
* contrib/lisp/org-panel.el (orgpan-panel): Make sure the panel buffer
is resized to four lines not the document buffer.
TINYCHANGE
---
contrib/lisp/org-panel.el | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/contrib/lisp/org-panel.el b/contrib/lisp/org-panel.el
inde
* contrib/lisp/org-panel.el: don't setq undefined and otherwise unused
variable orgpan-this-panel-window
* contrib/lisp/org-panel.el (orgpan-check-panel-mode): fix format
string of (error)
* contrib/lisp/org-panel.el: declare variables
viper-emacs-state-mode-list and viper-new-major-mode-buff
Handling of emphasized text is hard-coded in org-element.el.
Unfortunaly fixing this requires more than teaching
`org-element-text-markup-successor' about `org-emphasis-alist' because
separate `org-element-TYPE-{parser,interpreter} functions are used for
each type of emphasized text.
Wouldn't it
Hello,
Until a few months ago I was able to use `org-cycle' in
`emacs-lisp-mode' buffers, and it just worked after turning on
`outline-minor-mode' but not `orgstruct-mode'. I am using the
development versions of both Emacs (25.0.50) and Org (9.0).
But somewhere along the way `org-cycle' partiall
Nicolas Goaziou writes:
> `orgstruct-mode' really needs some love.
It's really hard to understand what is going on for someone not familiar
with the Org code. Furthermore I am not using the default Emacs
bindings (but I also tested with emacs -Q), so code that generates
commands and bindings,
> #+BEGIN_SRC emacs-lisp
> (add-hook 'elisp-mode-hook 'turn-on-orgtbl)
> (add-hook 'elisp-mode-hook
> (lambda ()
> (setq-local orgstruct-heading-prefix-regexp
> ";; ")))
> #+END_SRC
It appears the stupid thing I did was that I use
Aaron Ecay writes:
> Thorsten Jolitz wrote the outshine library
I know. I used it for a while and contributed a few commits. But I
pretty much only used the cycling functionality at the time and when
I discovered that `org-cycle' worked for that too, I stopped using
outshine. It also felt a b
Nicolas Goaziou writes:
> Hello,
>
> Jonas Bernoulli writes:
>
>> Thanks. But could you please change it to
>>
>> (if (or outline-minor-mode orgstruct-mode)
>> (call-interactively #'show-children)
>> ...)
>
> You could set `o
Nicolas Goaziou writes:
> Jonas Bernoulli writes:
>
>> Nicolas Goaziou writes:
>>
>>> Jonas Bernoulli writes:
>>>
>>>> Thanks. But could you please change it to
>>>>
>>>> (if (or outline-minor-mode orgstruct-mode)
&
Hello
Given this Org file
#+TITLE: Demo Manual
#+TEXINFO_DIR_CATEGORY: Emacs
#+TEXINFO_DIR_TITLE: Demo: (demo).
#+TEXINFO_DIR_DESC: Demo.
* Missing empty line
There is text between the heading and the menu
** There is text before this menu
** the empty line before Menu IS
The related `org-texinfo--build-menu' has a similar issue. Unlike
`org-texinfo-make-menu' which may end up not inserting a newline
when it should, it may end up removing a newline when it should not.
Given this Org file:
#+TITLE: Demo2 Manual
#+TEXINFO_DIR_CATEGORY: Emacs
#+TEXINFO_DIR_TIT
> Fixed. Thank you.
Thanks to you too!
Jonas
Hello,
Currently "#+OPTIONS: num:N" not only affects whether sections are
numbered, it also controls whether links to numbered sections look
like
See *note 5.2.3: Section hooks.
or
See *note Section hooks: Section hooks.
in the info file. Here the first seems better, but when looking at
t
Hello,
In the Magit manual I usually use separate nodes for sections and
subsections, but in a few cases a section's children should be part
of the section's node.
I accomplished that by adding an additional element property NONODE
and redefining `org-texinfo-headline' and `org-texinfo--menu-entr
> The property should probably be renamed to e.g. NOCHILDNODES, since it
> is the *children* of the section which has this option set that do not
> get any nodes of their own, not the section for which the property is
> set.
Ignore this. It is the section that has NONODE which does not get its
ow
I need to ensure that the texinfo exporter generates texi files that use
space for indentation even when the global value of indent-tabs-mode is t.
If tabs are used, then code blocks end up being intended wrong in the final
info file.
There are probably other more direct approaches to achieve this
Hi
So Gmail decided that your reply was spam...
On Sat, Dec 31, 2016 at 3:40 PM, Nicolas Goaziou
wrote:
>
> Could you provide an ECM?
>
What's an ECM?
>
> Besides, using `org-export-filter-final-output-functions' seems easier
> than your set up.
>
I'll try that, thanks.
Best regards,
Jonas
So here's the ECM:
* Node
#+BEGIN_SRC emacs-lisp
(progn (progn foo
bar))
#+END_SRC
It doesn't matter whether `bar))` is preceded, in the org file, by two tabs
or 16 spaces. In both cases it will be preceded by one tab followed by 7
spaces in the texi file; and by 5 spaces followed by one tab f
Thanks for the tip and sorry for the late response.
This seemed promising at first but let to all kinds of strange behavior.
Code-blocks that are part of a list item turned out to particularly
painful, as here "Finally, you can use ‘-i’ to preserve the indentation of
a specific code block" means t
17 at 3:46 PM, Nicolas Goaziou
wrote:
> Hello,
>
> Jonas Bernoulli writes:
>
> > This seemed promising at first but let to all kinds of strange behavior.
> > Code-blocks that are part of a list item turned out to particularly
> > painful, as here "Finally, you
I'll get back to you in a few days.
On Sat, Jan 14, 2017 at 6:52 PM, Nicolas Goaziou
wrote:
> Jonas Bernoulli writes:
>
> > I did notice myself that the two-space indentation for blocks that are
> part
> > of a list element are reserved and also that one can do what y
On Sat, Dec 31, 2016 at 3:40 PM, Nicolas Goaziou
wrote:
Besides, using `org-export-filter-final-output-functions' seems easier
> than your set up.
>
This approach works too. The following code produces exactly the same
result as what I posted earlier:
(defun ox-texinfo+--untabify (string back-e
On Sat, Jan 14, 2017 at 6:52 PM, Nicolas Goaziou
wrote:
>
>
> Could you show an ECM?
>
I was going to, but:
Turns out:
1. Whether -i is used doesn't matter here.
2. The reason these blocks are not intended the same way is that
SRC => @example or @lisp
EXAMPLE => @verbatim
3. What bothered
/s/indention/indentation/
And sorry for the earlier top-posting and generally awful formatting. For
some odd reason I subscribed using Gmail, and that is giving me some grieve.
On Sat, Jan 14, 2017 at 11:11 PM, Jonas Bernoulli
wrote:
> On Sat, Jan 14, 2017 at 6:52 PM, Nicolas Goaziou
>
I've run into these two feature inconsistencies:
- The command ~org-protocol-create-for-org~ does ~(require 'org-publish)~,
but that should now be ~ox-publish~.
- The command ~org-capture-import-remember-templates~ does ~(require
'org-remember)~, which makes sense because its purpose is to conver
> I don't think this is an issue. This function only makes sense if user
> has an old `org-remember' library lying around. Otherwise, it raises an
> error. This is the actual behaviour.
Makes sense, and is more friendly than the alternative.
> The other option is to remove the function altogether
Hello
While I realize I probably should not be using `org-cycle' in buffers in
which `outline-minor-mode' is enabled, I have been doing it for a long
time, and while that command certainly is overkill in such buffers, the
only problem I have run into is that I usually have to apply a tiny
patch to
Hello,
1) Starting with "1b415735e ox-texinfo: Small menu refactoring"
a menu contains not only entries for subnodes but recursively
for all subsub...nodes.
That's because `org-element-map' is no longer called with `headline'
as NO-RECURSION.
You can use this trivial source to ver
Hello,
For some reason the authors of `makeinfo' thought it would be a good
idea to split the generated info file into two files by default once
its size reaches a certain undocumented threshold.
When that happened to me for the first time I was very surprised and
thought that "foo-1.info" and "f
Me again,
For the most part Org now honors the file-local value of
`indent-tabs-mode' as set in an Org file. When that value is `nil' and
a buffer used to edit a source block from that file contains lines that
begin with tabs, then those tabs are being replaced with spaces before
the text is writ
>> Please consider making this the default value.
>
> I agree that makes sense. Done.
Thanks!
> I suggest to use a hook instead (maybe `org-tab-first-hook' or some
> such).
Alright. I have decided to go with `outline-magic.el'.
After some modernization it seems to work well. I don't remember what
the problem was the last time I tried. I will probably publish my
updated version eventuall
Hello
In 499c0a50cc4b11e37b91374af23cb27ab8fc20d2 some libraries were
renamed, but some other libraries continue to depend on the old
features:
- lisp/ox-icalendar.el still depends on org-bbdb
- contrib/lisp/org-bibtex-extras.el still depends on org-bibtex
Overall this change did not cause too m
Please consider applying the below patch, which fixes many spelling
errors. I did not write a commit message that lists every file and
function/variable that happened to contain a typo. That seems rather
unnecessary for this type of change, but if you want that I can do it.
In addition to the be
h /that/ however is that the author has been inactive for
> several years now, with the package being maintained by Jonas Bernoulli,
> who I did not yet contact.
I don't actually use it myself and just enable it temporarily if someone
reports a bug or something. It's not that I am not
> Org-mode 9.1 is out!
Congratulations!
This was discussed here: https://github.com/hniksic/emacs-htmlize/issues/7.
> Bastien, can you please look at this?
And once you do, please also consider making the repository (and the
webpage) available over https. Only very few packages remain that use
Git without making a man-in-the-middle attack impossible. The Org team
follows best practices in most cases where oth
There is a typo in the first word of the README.
I was surprised to learn that it existed for five years.
Cheers,
Jonas
ges.
>
> This manual is for Borg version 2.0.0 (v2.0.0-59-g89a9394+1).
>
> Copyright (C) 2016-2018 Jonas Bernoulli
> ...
It is already possible to set the section whose content is to be used
on the copyright page (and which can be inserted elsewhere using
"#+texinfo: @inser
Nicolas Goaziou writes:
>
> Jonas Bernoulli writes:
>
>> Currently ox-texinfo uses the text before the first Org section as the
>> "Top" Info node. That is fine for manuals like org-manual.org where
>> that part of the document only consists of a few lin
> A blind guess: Try to run make clean?
Didn't help here.
I have added
(with-eval-after-load 'org
(require 'org-element))
to my init.el as a temporary workaround.
Hello,
In the olden days before Org's own manual was written using an org-mode
file, I started doing just that for Magit. Because ox-texinfo.el wasn't
quite there yet I wrote an extension, ox-texinfo+.el, to fill in the
gaps. Since then I have written seven more manuals that use my
extension.
I
Nicolas Goaziou writes:
> I like the idea, thank you for suggesting it.
Great :D
>>#+TEXINFO_DEFFN: t
>
> The chosen UI is rather odd however. I cannot think of another use of
> controlling export thhough "#+keyword: boolean" syntax. Usually, we
> extend the "options" keyword. It could becom
Sorry for the delay, I got side-tracked with many other things.
Nicolas Goaziou writes:
>>> It is possible to mix the two styles;
>>
>> Well... it turned out not to be true, but I should be able to get it
>> to work.
>
> Then I suggest to use "attr_texinfo" keyword, for example:
>
>#+attr_te
* doc/org-manual.org (Plain lists in Texinfo export): Reorder and
document new functionality.
* lisp/ox-texinfo.el (org-texinfo--filter-parse-tree)
(org-texinfo--normalize-items): New functions.
* lisp/ox-texinfo.el (org-texinfo-item): Use @itemx or @item
depending on the used bullet.
---
doc/org-
n more detail in the manual, which I
have updated. The other styles that are used in Org's own manual are
not affected and both styles can be used in the same manual.
Cheers,
Jonas
Jonas Bernoulli (2):
ox-texinfo: Turn a description list item with "+" bullet into @it
* doc/org-manual.org (Plain lists in Texinfo export): Document use
of definition command prefixes in description lists.
* lisp/ox-texinfo.el (org-texinfo--definition-command-alist)
(org-texinfo--definition-command-regexp): New variables.
* lisp/ox-texinfo.el (org-texinfo--filter-parse-tree): Call
Nicolas Goaziou writes:
> Hello,
>
> Thanks. Some comments follow.
Thanks for the review!
> Jonas Bernoulli writes:
>
>> +In description lists the used bullet is significant when exporting to
>> +Texinfo; when in doubt, then use =-=. An item that uses =+= instead
Nicolas Goaziou writes:
> There's a mismatch between the keys.
Fixed.
> Simply put:
>
> Command in parenthesis, as done above, is optional.
Done.
>> +Regardless of which approach you use, you must define the =kbd= macro
>> +(see [[*Macro Replacement]]), which you can then use anywhere in the
Nicolas Goaziou writes:
>> For example:
>>
>> - Key: C-c C-w (forge-browse-TYPE) ::
>> + Key: C-c C-w (forge-browse-dwim) ::
>> + Key: N b I (forge-browse-issues) ::
>> + Key: N b P (forge-browse-pullreqs) ::
>> + Key: N b t (forge-browse-topic) ::
>> + Key: N b i (forge-browse-issue) ::
>> + Key
Nicolas Goaziou writes:
> Hello,
>
> Jonas Bernoulli writes:
>
>> Would it be okay to represent e.g. "C-c SPC" as:
>>
>>(export-snippet
>> (:back-end "texinfo" :value "@kbd{C-c @key{SPC}}" :post-blank 0 :parent
>>
I think I have addressed all you feedback.
The only difference when exporting org-manual.org is:
-When typing text into a field, Org treats @kbd{DEL},
+When typing text into a field, Org treats @kbd{@key{DEL}},
Jonas Bernoulli (3):
ox-texinfo: Add function for use by kbd macro
ox-texinfo
* doc/org-manual.org (Plain lists in Texinfo export): Reorder and
document new functionality.
* lisp/ox-texinfo.el: Add org-texinfo--combine-items to the list of
:filter-parse-tree functions of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo--combine-items) New function.
* lisp/ox-texinfo.el
* doc/org-manual.org (Plain lists in Texinfo export): Document use
of definition command prefixes in description lists.
* lisp/ox-texinfo.el: Add org-texinfo--separate-definitions to the
list of :filter-parse-tree functions of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo--quoted-keys-rege
* doc/doc-setup.org: Use org-texinfo-kbd-macro for kbd macro.
* doc/org-manual.org: Add new node "Key bindings in Texinfo export".
* lisp/ox-texinfo.el (org-texinfo-kbd-macro): New function.
---
doc/doc-setup.org | 2 +-
doc/org-manual.org | 27 +++
lisp/ox-texinfo.el | 2
Hello Nicolas,
Could you please have another look?
Cheers,
Jonas
Jonas Bernoulli writes:
> I think I have addressed all you feedback.
>
> The only difference when exporting org-manual.org is:
>
> -When typing text into a field, Org treats @kbd{DEL},
> +When typing
The code is the same as in v3, but I noticed that I had forgotten
to update one of the doc-strings, so that's fixed here.
Cheers,
Jonas
Jonas Bernoulli (3):
ox-texinfo: Add function for use by kbd macro
ox-texinfo: Optionally use @itemx for certain description list items
* doc/org-manual.org (Plain lists in Texinfo export): Reorder and
document new functionality.
* lisp/ox-texinfo.el: Add org-texinfo--combine-items to the list of
:filter-parse-tree functions of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo--combine-items) New function.
* lisp/ox-texinfo.el
* doc/org-manual.org (Plain lists in Texinfo export): Document use
of definition command prefixes in description lists.
* lisp/ox-texinfo.el: Add org-texinfo--separate-definitions to the
list of :filter-parse-tree functions of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo--quoted-keys-rege
* doc/doc-setup.org: Use org-texinfo-kbd-macro for kbd macro.
* doc/org-manual.org: Add new node "Key bindings in Texinfo export".
* lisp/ox-texinfo.el (org-texinfo-kbd-macro): New function.
---
doc/doc-setup.org | 2 +-
doc/org-manual.org | 27 +++
lisp/ox-texinfo.el | 2
Nicolas Goaziou writes:
>> + (t
>> +(org-element-set-contents
>> + item (nconc
>> + (mapcar (lambda (key) `(keyword (:key "KINDEX" :value ,key)))
>> kindex)
>> + (mapcar (lambda (cmd) `(keyword (:key "FINDEX" :value ,cmd)))
>> findex)
>> + (org-elemen
Nicolas Goaziou writes:
>> #+begin_example
>> -,#+ATTR_TEXINFO: :table-type vtable :sep , :indic asis
>> +,#+attr_texinfo: :table-type vtable :indic asis :sep ,
>> - foo, bar :: This is the common text for variables foo and bar.
>> #+end_example
>
> This change is not needed. Org markup is cap
Nicolas Goaziou writes:
>> +(defun org-texinfo--massage-key-item (plain-list item args)
>> + "In PLAIN-LIST modify ITEM based on ARGS.
>> +Reformat ITEM's tag property and add findex and kindex entries to
>> +its content. If the bullet is \"+\" then use \"@itemx\" and deal with
>> +data from pr
Nicolas Goaziou writes:
> I suggest to require a special attribute before doing so, e.g.,
>
> #+attr_texinfo: :compact t
> - key: a ::
> - key: b ::
>
> - key: c ::
> - key: d ::
I have noticed that I accidentally called it ":combine" in the
documentation and have fixed that. (Do you
* doc/doc-setup.org: Use org-texinfo-kbd-macro for kbd macro.
* doc/org-manual.org: Add new node "Key bindings in Texinfo export".
* lisp/ox-texinfo.el (org-texinfo--quoted-keys-regexp): New variable.
* lisp/ox-texinfo.el (org-texinfo-kbd-macro): New function.
---
doc/doc-setup.org | 2 +-
doc/o
* doc/org-manual.org (Plain lists in Texinfo export): Document use
of definition command prefixes in description lists.
* lisp/ox-texinfo.el: Add org-texinfo--separate-definitions to the
list of :filter-parse-tree functions of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo--definition-comma
We are getting closer, I think.
Tested with the Org and Magit manuals again. Passed.
Jonas Bernoulli (3):
ox-texinfo: Add function for use by kbd macro
ox-texinfo: Optionally use @itemx for certain description list items
ox-texinfo: Define definition commands using description lists
doc
Nicolas Goaziou writes:
>> - (items (and tag
>> - (let ((tag (org-export-data tag info)))
>> + (items (org-element-property :itemx item))
>> + (items (cond (items
>> + (mapcar (lambda (tag) (org-export-data tag info))
>> + (n
* doc/org-manual.org (Plain lists in Texinfo export): Reorder and
document new functionality.
* lisp/ox-texinfo.el (org-texinfo-item): In a description list when
its :compact attribute is non-nil, then transcode consecutive items
using one @item and one or more @itemx commands, if all of them
excep
Small fix:
- (memq (org-element-property :post-blank previous-item)
- '(1 nil)))
+ (eq 1 (org-element-property :post-blank item)))
* doc/doc-setup.org: Use org-texinfo-kbd-macro for kbd macro.
* doc/org-manual.org: Add new node "Key bindings in Texinfo export".
* lisp/ox-texinfo.el (org-texinfo--quoted-keys-regexp): New variable.
* lisp/ox-texinfo.el (org-texinfo-kbd-macro): New function.
---
doc/doc-setup.org | 2 +-
doc/o
"compact-itemx" as the name of the export option but it seems
that the names of most other options are much shorter, so maybe just
"itemx" would be better. I am a bit unsure about the name of the
variable as well.
Regards,
Jonas
Jonas Bernoulli (4):
ox-texinfo: Add
* doc/org-manual.org (Plain lists in Texinfo export): Reorder and
document new functionality.
* lisp/ox-texinfo.el (org-texinfo-item): In a description list when
its :compact attribute is non-nil, then transcode consecutive items
using one @item and one or more @itemx commands, if all of them
excep
* doc/org-manual.org (Plain lists in Texinfo export): Document use
of definition command prefixes in description lists.
* lisp/ox-texinfo.el: Add org-texinfo--separate-definitions to the
list of :filter-parse-tree functions of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo--definition-comma
* doc/org-manual.org (Plain lists in Texinfo export): Document the
:texinfo-compact-itemx export option and variable
org-texinfo-compact-itemx.
* lisp/ox-texinfo.el: Add org-texinfo-compact-itemx to the
:options-alist of the texinfo backend.
* lisp/ox-texinfo.el (org-texinfo-compact-itemx): New opt
Nicolas Goaziou writes:
> Applied. Thank you! We can always revisit the variable name later.
Thanks to you too!
> Could you provides an ORG-NEWS entry for this?
Will do.
Cheers,
Jonas
---
etc/ORG-NEWS | 19 +++
1 file changed, 19 insertions(+)
diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index 5a94e737e..fd29d39d7 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -63,6 +63,20 @@ list of various table options (between brackets in LaTeX
export),
since certain tabular
on't know whether this has to be misspelled to function as
expected, so I did't fix the typo.
Jonas Bernoulli (1):
Fix typos
contrib/lisp/org-depend.el | 4 ++--
doc/org-manual.org | 2 +-
lisp/org-clock.el | 2 +-
lisp/org.el| 2 +-
mk/server.mk
---
contrib/lisp/org-depend.el | 4 ++--
doc/org-manual.org | 2 +-
lisp/org-clock.el | 2 +-
lisp/org.el| 2 +-
mk/server.mk | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/contrib/lisp/org-depend.el b/contrib/lisp/org-depend.e
Hello,
If a code-block that is supposed to produce a table returns an empty
list, then nothing at all is inserted, as demonstrated by the second
example below:
#+begin_src emacs-lisp :results table
;; Some sql query that returns one or more rows:
'(("foo" "bar"))
#+end_src
#+RESULTS:
| foo |
Ihor Radchenko writes:
> Jonas Bernoulli writes:
>
>> It used to behave like that before 51a628bc5efc from 2009, which started
>> turning all symbols, including nil, into strings, but without giving any
>> reason why that should be done.
>>
>> It has work
* lisp/ob-ref.el (org-babel-ref-resolve): When the result an empty
list, then treat it as a list, not as the symbol nil.
* testing/lisp/test-ob.el (test-ob/return-empty-list-from-post-block):
Add new test.
* etc/ORG-NEWS (Post-processing code blocks can return an empty list):
Document change in beh
Here's my patch, including a test and a news entry.
I didn't know where to put the test so I just put it at the beginning.
It should probably be moved.
Jonas Bernoulli (1):
Allow returning empty list from post-processing block
etc/ORG-NEWS| 6 ++
lisp/ob-ref.el
* lisp/ob-ref.el (org-babel-ref-resolve): When the result an empty
list, then treat it as a list, not as the symbol nil.
* testing/lisp/test-ob.el (test-ob/post-header-arguments): Add new
test.
* etc/ORG-NEWS (Post-processing code blocks can return an empty list):
Document change in behavior.
---
By Emacs' convention all messages should begin with a capital letter.
lisp/ob-awk.el (org-babel-expand-body:awk):
lisp/ob-core.el (org-babel-execute-src-block):
lisp/ob-groovy.el (org-babel-execute:groovy):
lisp/ob-maxima.el (org-babel-execute:maxima):
lisp/ob-sed.el (org-babel-execute:sed):
Begin
annoyance.
Jonas Bernoulli (2):
Don't print arguments of post-process arguments to stdout
Begin messages about executing code blocks with a capital letter
lisp/ob-awk.el| 2 +-
lisp/ob-core.el | 2 +-
lisp/ob-emacs-lisp.el | 2 +-
lisp/ob-groovy.el | 2 +-
lisp/ob-ma
It is unclear whether the arguments were printed on purpose. It might
be useful to do so at times for debugging purposes, but generally they
drown out other messages when a lot of post-processing is being done;
making it harder to spot messages of interest that would otherwise
allow noticing regre
`org-babel-script-escape' doesn't handle an empty python list
correctly; ['a'] => ("a") but [] => [].
#+name: addheader
#+header: :var rows=""
#+begin_src python
return []
#+end_src
#+header: :post addheader(*this*)
#+begin_src emacs-lisp :results table
nil
#+end_src
#+RESULTS:
: []
An emp
Ihor Radchenko writes:
> Jonas Bernoulli writes:
>
>> `htmlize' is currently maintained at https://github.com/hniksic/emacs-htmlize
>> but its maintainer hasn't been responding to any issues and pull-requests
>> for quite some time now and seems to be inac
Ihor Radchenko writes:
> Adding Jonas to the loop.
>
> For some more context, we are willing to help maintaining orphan
> Org-related packages if the requests are submitted to Org mailing list.
Thanks, and sorry I forgot about this. I'll have to think about it some
more before I can make any ge
Ihor Radchenko writes:
> So, we now have https://orgmode.org/worg/org-orphanage.html
I just went through the list of packages mentioned there as being hosted
on https://github.com/emacsorphanage:
- org-grep should be delisted as it found a new home at
https://sr.ht/~minshall/org-grep/
- ox-p
g Github to report issues in favour of Org mailing
>> list.
>
> I see, and I agree, especially if issues against Org orphan packages
> are to be reported on the Org mailing list at some point.
>
> Shall I create https://git.sr.ht/~bzg/org-orphan-packages ?
>
>> Otherwise, I h
Ihor Radchenko writes:
> What about https://github.com/flexibeast/org-vcard and
> https://github.com/nikclayton/ob-sql-mode ?
Are you saying these packages are unmaintained and asking whether they
should be moved to the orphanage?
When I feel like that about a package, I usually open an issue o
Bastien Guerry writes:
> Sounds good to me too, I'm "bzg" on GitHub. Thanks!
Invitation sent.
Please make your "membership" public at
https://github.com/orgs/emacsorphanage/people.
Welcome!
:D
1 - 100 of 117 matches
Mail list logo
