[PATCH] lisp/lisp/ob-core.el (org-babel-merge-params): Rename plists to alists
Hello! I noticed that in the function org-babel-merge-params the arguments are alists rather than plists. To this end, I created a patch that updates the relevant variable names as well as the docstring (see attachment). From db9d5b77aedfb87aa0a3382f6be9d5921eef2ffd Mon Sep 17 00:00:00 2001 From: Matthias Hetzenberger Date: Sat, 22 Jun 2024 16:06:41 +0200 Subject: [PATCH] org-babel-merge-params: Rename plists to alists --- lisp/ob-core.el | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/lisp/ob-core.el b/lisp/ob-core.el index db75f1f0a..5b32f503b 100644 --- a/lisp/ob-core.el +++ b/lisp/ob-core.el @@ -2959,9 +2959,9 @@ used as a string to be appended to #+begin_example line." (goto-char body-start) (insert body -(defun org-babel-merge-params (&rest plists) - "Combine all parameter association lists in PLISTS. -Later elements of PLISTS override the values of previous elements. +(defun org-babel-merge-params (&rest alists) + "Combine all parameter association lists in ALISTS. +Later elements of ALISTS override the values of previous elements. This takes into account some special considerations for certain parameters when merging lists." (let* ((results-exclusive-groups @@ -2990,8 +2990,8 @@ parameters when merging lists." ;; Some keywords accept multiple values. We need to treat ;; them specially. vars results exports) -(dolist (plist plists) - (dolist (pair plist) +(dolist (alist alists) + (dolist (pair alist) (pcase pair (`(:var . ,value) (let ((name (cond -- 2.45.1
Bug: clocktable latex attributes
Hi the Orgmode team, I have a problem with the clocktable which seems to be a
bug because it does not accept latex attributes before the BEGIN
line:#+latex_header: \usepackage{tabularx}#+ATTR_LATEX: :align Xll :width
\textwidth#+BEGIN: clocktable :scope file :maxlevel 2 the only solution I found
is the following (put the attribute after the BEGIN :):#+latex_header:
\usepackage{tabularx}#+BEGIN: clocktable :scope file :maxlevel 2#+ATTR_LATEX:
:align Xll :width \textwidth But every time I update the clocktable (C-c C-c)
the latex attribute line disappears. Cordially. Matt
Bug: clocktable
Salut l’équipe d’Orgmode,
J’ai un soucis avec le clocktable qui semble être un bug car il n’accepte pas
les attributs latex avant la ligne BEGIN:
#+latex_header: \usepackage{tabularx}
#+ATTR_LATEX: :align Xll :width \textwidth
#+BEGIN: clocktable :scope file :maxlevel 2
la seul solution que j'ai trouvé, c'est la suivante (mettre l’attribut après le
BEGIN :) :
#+latex_header: \usepackage{tabularx}
#+BEGIN: clocktable :scope file :maxlevel 2
#+ATTR_LATEX: :align Xll :width \textwidth
Mais à chaque fois que je met à jour le clocktable (C-c C-c) la ligne
d'attribut latex disparait.
Cordialement.
Matt
openpgp-digital-signature.asc
Description: PGP signature
[O] Agenda display count of monthly anniversary
Hi all, I know I can display the number of years since an anniversary using diary-anniversary. However, I would like to also achieve this with monthly anniversaries. For example the count of occurences of the event <2019-05-25 So. +1m> should be displayed in the agenda view. Is there any easy possibility to achieve this? Regards, Matthias
Re: [O] HTML Export - Footnotes inconcistency
Hello, Nicolas Goaziou writes: > This is intended, in a way, since the inline footnote is not a paragraph > by itself. It is contained within a paragraph. This explains why you > cannot have blank lines within an inline footnote. I think I get the logic behind it. The problem is the inconsistency it creates for the viewer. Does it really matter for them if I wrote my footnote inline or not? Thanks for your answer. -- Matthias Paulmier
[O] HTML Export - Footnotes inconcistency
Hello, I came across this problem today (or maybe it is intended but I couldn't find any explanation in the docs). There is an inconsistency on how inline/anonymous and named footnotes are exported in HTML. For example, with the following source: --8<---cut here---start->8--- #+TITLE: Testing footnotes #+LANGUAGE: en Testing[fn::test1] footnotes[fn:2] [fn:2] test2 --8<---cut here---end--->8--- Exports to this : --8<---cut here---start->8--- Footnotes: 1 test1 2 test2 --8<---cut here---end--->8--- We can see here that the named footnote creates a paragraph of the same class as the parent container "footpara" whereas the inlined one doesn't create this. If this is intended, why? If not, which is the intended one? Reagards. -- Matthias Paulmier
[O] Default emphasis regexp problems
Hi,
the following cases fail to display italics correctly in org-mode 7.4:
- snip -
1. The user would also certainly think that “it’s all actually happening,”
simply because it /would be happening,/ albeit in an environment that is
different from the physical one his body is located in. We seem to have much
less difficulty than Jones acknowledging that one is able to perform such
activities in a /shared/ environment.
2. Obviously, cooking a dish presupposes that there /is/ a dish to be cooked.
Therefore, a crucial question in evaluating the possibility of cooking a dish
would be /whether there is food inside the kitchen,/ which the user could
process without leaving the virtual world. If this were the case, and we would
still uphold Jones’s judgement that cooking in a virtual world is impossible,
then indeed we would be confronted with something or other. If, on the other
hand, the impossibility of cooking a dish is due to the fact that there simply
/are/ no dishes inside that environment, then Jones’s criticism does not apply
to virtual environments at all.
3. This is another way in which we can understand Jones’s remark about there
being “no way [the dish] /is./” This is not an uncommon position.
- snip -
Including punctuation in italics passages is (as I understand it) preferred from
a typography point of view, but it breaks org-mode's emphasis regexp. An ad-hoc
adjustment of the default Emphasis Regexp Components solves the problem:
-- fix begin
Org Emphasis Regexp Components: Hide Value
Allowed chars in pre : " ('\"{"
Allowed chars in post : "- .,:!?;'\")}\\”"
Forbidden chars in border : " ^M\n'"
Regexp for body : "."
-- fix end --
As far as I can see, the change does not break anything, but I am not sure,
because I don't really understand the rationale behind all the choices in the
original regexp. Perhaps its author can have a look at my changes?
I suggest that the default be changed to fix the above problems, since the
normal user cannot be expected to fix the regexp himself.
Thanks!
A.M.
[Orgmode] Re: A few questions about how you write e-mails
On 10/21/2010 10:10 AM, suvayu ali wrote: > On 20 October 2010 20:40, Nick Dokos wrote: >> Given the mangling that mailers do to replies (e.g. the idiotic default >> top posting of Thunderbird and its ilk), how they handle signatures, and >> the non-standard nature of signatures themselves, I'd say this is pretty >> much hopeless. > > After our discussion yesterday, I did some research. Didn't find > anything +ve. I am considering switching to mutt. :) Hello!! I didn't read the entire thread on this, but I like to add that Thunderbird can be customized in where and how it posts the original message in replies (Account Settings -> Composition). AND it has support for an external editor [0]. I'm using Thunderbird 3 + emacs. You even can use a single Profile cross-platform! However, thanks for boxquote.el, it's pretty nice! [0] http://globs.org/articles.php?pg=2&lng=en Download and install "External Editor" and set it to launch a simple emacsclient ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Wanted: org-publish-org-to-ascii
Am 13.10.2010 21:12, schrieb Juan Pechiar: On Wed, Oct 13, 2010 at 07:59:23PM +0200, Manuel Danzl wrote: I'm a happy org-mode user since a few month's and I'm using org-publish to write on some work related documentation. Now my collegues asked me to export the docs not only to html but also to plain text! Unfortunately, org-mode currently lacks a publishing function exporting to ascii, so I kindly ask you to implement it. Copying from the definition for org-publish-org-to-html: #+BEGIN_SRC: emacs-lisp (defun org-publish-org-to-ascii (plist filename pub-dir) "Publish an org file to ASCII. See `org-publish-org-to' to the list of arguments." (org-publish-with-aux-preprocess-maybe (org-publish-org-to "ascii" plist filename pub-dir))) #+END_SRC you can even use "utf8" instead of "ascii". Then use the newly defined org-publish-org-to-ascii as the :publishing-function in your publish project. Not tested, you try it :-) Regards, .j. That did the job! Thanks Juan. I can now publish to html and txt. Very nice. Sorry I've created a lot of confusion, cause some people thought, I was talking about the =export= function, not the =publish= function. Thanks for all the replies though. I even Manuel ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] skip entry with inherited tags
Moin, I'm using a simple skip-function to exclude todos from a list. (defun my-skip-someday-and-scheduled () "" (org-agenda-skip-entry-if 'scheduled 'regexp ":SOMEDAY:")) That works when the tag was assigned to an entry but not when it was inherited from a parent. How do I get all tags for an entry? Many thanks Matthias ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Passing a table to org-babel shell script
On 11:33 Sat 06 Feb, Eric Schulte wrote: Moin, thanks for your reply > 1) allowing the user to specify a separator with a header argument as >follows >#+begin_src sh :var table=sec :separator , > cat < $table > EOF >#+end_src > >which would result in something like > >: "Hello, World" I like this idea because it is what I would expect. In my first "experiment", I assumed that I can use the "|" as a separator. I would like to use a table as input form and pipe the rows to a shell script written in org-babel. Sometimes it is easier to proccess data with awk instead of using elisp. So my example is a bit misleading. > 2) writing the table to a tab or comma separated file and then >replacing =$table= in the source block body with the path to the >file name, s.t. something like IMHO it is not necessary under Unix. Reading from stdin is usual. But it maybe different under Windows. Many thanks Matthias ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Passing a table to org-babel shell script
Hello, I try to use a org-mode table as input to an shell script. It works, if I use a Table with one column. #+tblname: sec | Hello World | #+begin_src sh :var table=sec cat
