Re: [BUG] Infinite loop in org-agenda-show-new-time
Hi Matthew, not sure I replied to this one but in case I didn't, yes, my initial fix was wrong, I reverted it. Thanks! -- Bastien
Re: [org-inlinetask] Inquiry of opinion from all users
D writes: > Thank you in advance, PS: I don't use org-superstar-mode (yet) so I can't really answer your questions, but I hope others will do. -- Bastien
Re: Fixed vs variable pitch font [legibility 4/6]
Hi Texas, Texas Cyberthal writes: > Why does there need to be an Org version of mixed-pitch-mode? It > already works for Org. Yes, indeed. PS: Speaking of good defaults, I think quoting emails with ">" instead of #+begin_quote is way more readable. -- Bastien
Re: [BUG?] org-babel-lilypond-commands can't be set through customize
Hi Victor, thanks for reporting this, this is fixed now in the maint branch. Best, -- Bastien
Re: Fixed vs variable pitch font [legibility 4/6]
#+begin_quote Bastien > Having said that, if Org could have a simple org-mixed-pitch-mode, or > something like that, that could be very helpful, since it could make > such configuration much easier. If anyone wants to start coding something like this, we can consider referencing it on Worg. #+end_quote Why does there need to be an Org version of mixed-pitch-mode? It already works for Org. https://gitlab.com/jabranham/mixed-pitch
Re: Bug: broken org-cycle-include-plain-lists integrate [9.3.3 (9.3.3-elpa @ /home/bruce/.emacs.d/elpa/org-9.3.3/)]
Hi Bruce, > * Bug Report > > (setq org-cycle-include-plain-lists 'integrate) > > seems to have no effect. Thanks for reporting this. Fixed now. This was the consequence of this commit: https://code.orgmode.org/bzg/org-mode/commit/c2aebcee27 Best, -- Bastien
Re: Bug: broken org-cycle-include-plain-lists integrate [9.3.3 (9.3.3-elpa @ /home/bruce/.emacs.d/elpa/org-9.3.3/)]
Hi Stardiviner, stardiviner writes: > This this related to recently new added option value. the option was introduced just 2-3 hours before Bruce reported his problem ;) > #+begin_src emacs-lisp > (setq org-adapt-indentation 'headline-data) > #+end_src > > It is introduced in commit "e3b79ad2bf7ab7b91c0ad2b8383d639bfe154ce7". Which > might breaks indentation of plain list etc. I hope e3b79ad2 won't break anything but you're right, it can. Thanks, -- Bastien
Re: Bug: broken org-cycle-include-plain-lists integrate [9.3.3 (9.3.3-elpa @ /home/bruce/.emacs.d/elpa/org-9.3.3/)]
This this related to recently new added option value.
#+begin_src emacs-lisp
(setq org-adapt-indentation 'headline-data)
#+end_src
It is introduced in commit "e3b79ad2bf7ab7b91c0ad2b8383d639bfe154ce7". Which
might breaks indentation of plain list etc.
Bruce Tulloch writes:
> * Bug Report
>
> (setq org-cycle-include-plain-lists 'integrate)
>
> seems to have no effect.
>
> That is, plain lists are no longer cycling as children of outline headings.
>
> * Example
>
> This content appears when cycling on Example
>
> * This plain list line appears (correct)
> * this line also appears (incorrect)
> * this one too (it shouldn't)
> * but this one should appear (and does)
> * as does this one but
> * this should not (but does)
> * and so does this one
> * Discussion
>
> When cycling on the heading, plain lists always appears in the expanded
> state
> since upgrading to 9.3.3. The plain list will not cycle (as children of the
> heading). It appears that when org-cycle-include-plain-lists is 'integrate
> it
> is behaving the same as when set to t.
>
> This changed has appeared since 9.2.1 (which used to work).
> * Current State
> #+begin_src elisp
> (setq org-src-mode-hook '(org-src-babel-configure-edit-buffer
> org-src-mode-configure-edit-buffer)
> org-link-shell-confirm-function 'yes-or-no-p
> org-html-head-include-scripts nil
> org-metadown-hook '(org-babel-pop-to-session-maybe)
> org-export-with-sub-superscripts '{}
> org-clock-out-hook '(org-clock-remove-empty-clock-drawer)
> org-html-format-inlinetask-function
> 'org-html-format-inlinetask-default-function
> org-edit-src-content-indentation 0
> org-odt-format-headline-function 'org-odt-format-headline-default-function
> org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
> org-cycle-include-plain-lists 'integrate
> org-archive-location "ARCHIVE.org::* %s"
> org-mode-hook '(org-tempo-setup org-clock-load
> navi-make-org-mode-promotion-headings-list #[0 "\301\211 \207"
>[imenu-create-index-function org-imenu-get-tree] 2]
> #[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-hook
> org-show-all append local] 5]
> #[0 "\300\301\302\303\304$\207" [add-hook change-major-mode-hook
> org-babel-show-result-all append local] 5]
> org-babel-result-hide-spec org-babel-hide-all-hashes)
> org-clock-persist 'history
> org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
> org-archive-hook '(org-attach-archive-delete-maybe)
> org-confirm-elisp-link-function 'yes-or-no-p
> org-group-tags nil
> org-clock-history-length 50
> org-reverse-note-order t
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-metaup-hook '(org-babel-load-in-session-maybe)
> org-bibtex-headline-format-function #[257 "\300 \236A\207" [:title] 3
> "\n\n(fn ENTRY)"]
> org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
> org-babel-pre-tangle-hook '(save-buffer)
> org-file-apps '((auto-mode . emacs) ("\\.mm\\'" . default)
> ("\\.x?html?\\'" . default) ("\\.pdf\\'" . "evince %s"))
> org-tab-first-hook '(org-babel-hide-result-toggle-maybe
> org-babel-header-arg-expand)
> org-hide-leading-stars t
> org-export-initial-scope 'subtree
> org-html-text-markup-alist '((bold . "%s") (code .
> "%s") (italic . "%s")
> (strike-through . "%s") (underline . " class=\"underline\">%s")
> (verbatim . "%s"))
> org-hide-emphasis-markers t
> org-link-file-path-type 'relative
> org-ascii-format-drawer-function #[771 " \207" [] 4 "\n\n(fn NAME
> CONTENTS WIDTH)"]
> org-attach-store-link-p 'attached
> org-catch-invisible-edits 'error
> org-occur-hook '(org-first-headline-recenter)
> outline-minor-mode-hook '(outshine--outline-minor-mode-hook)
> org-log-into-drawer t
> org-export-before-processing-hook
> '(org-blackfriday--reset-org-blackfriday--code-block-num-backticks)
> org-html-head-include-default-style nil
> org-html-htmlize-output-type 'css
> org-cycle-hook '(org-cycle-hide-archived-subtrees
> org-cycle-show-empty-lines
> org-optimize-window-after-visibility-change)
> org-speed-command-hook '(org-speed-command-activate
> org-babel-speed-command-activate)
> org-odt-format-inlinetask-function 'org-odt-format-inlinetask-default-function
> org-clock-display-default-range 'untilnow
> org-confirm-shell-link-function 'yes-or-no-p
> ("eww" :follow eww :store org-eww-store-link) ("rmail" :follow
>org-rmail-open :store org-rmail-store-link)
> ("mhe" :follow org-mhe-open :store org-mhe-store-link)
> ("irc" :follow org-irc-visit :store org-irc-store-link :export
> org-irc-export)
> ("info" :follow org-info-open :export org-info-export :store
> org-info-store-link)
> ("gnus" :follow org-gnus-open :store org-gnus-store-link)
> ("docview" :follow org-docview-open :export org-docview-export
> :store org-docview-store-link)
> ("bibtex" :follow org-bibtex-open :store org-bibtex-store-link)
> ("bbdb" :follow org-bbdb-open :export org-bbdb-export :complete
>
Re: org-babel strange html print in R
You should try ~:results value html~. Here is what I got correctly: #+begin_src R :results value html library(xtable) x <- rnorm(100) y <- x + rnorm(100) print(xtable(summary(lm(y ~ x))),type="html") #+end_src #+RESULTS[<2020-02-11 13:14:59> 91ff0df2529284897e3585e3ec2e640290ee8308]: #+begin_export html Estimate Std. Error t value Pr(|t|) (Intercept) -0.0064 0.1069 -0.06 0.9520 x 1.1066 0.1022 10.83 0. #+end_export Jeremie Juste writes: > Hello, > > I've found that some strange results when outputing html from R. > Do you have some insights on a potential solution? > > Best regards, > Jeremie > > Org mode version 9.3.4 (9.3.4-elpa @ /home/djj/.emacs.d/elpa/org-20200206/) > > #+PROPERTY: header-args:R :eval yes :exports results :colnames yes :results > output :output-dir images/:cache yes :session *R* > > #+begin_src R :results output html > library(xtable) > x <- rnorm(100) > y <- x + rnorm(100) > print(xtable(summary(lm(y ~ x))),type="html") > #+end_src > > > #+RESULTS: > #+begin_export html > > > > > < > < > < > Estimate < > Std. Error < > t value < > Pr(|t|) > < > (Intercept) -0.0130 0.1023 -0.13 0.8991 > < > x 1.0011 0.0987 10.14 0. > > #+end_export > > > ** Expected results > #+begin_export html > > Estimate Std. Error t value > Pr(|t|) > (Intercept) -0.0130 > 0.1023 -0.13 align="right"> 0.8991 > x 1.0011 align="right"> 0.0987 10.14 > 0. > > #+end_export -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[SOLVED] Re: commit "328c9a1af * bad org.el: Enhance menus" caused error
Bastien writes: > Hi Stardiviner, > > I fixed this in master, thanks for reporting this bug. > > Best, Thanks Bastien, You're very active recently. I saw you fixed lot of issues and new patches. Thanks, really. -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
Short captions
I am having trouble understanding how short captions are supposed to work.
Consider this org document:
#+begin_src org
,#+title: Short Caption Test
,#+author: Org User
,#+label: table1
,#+caption[This is table1]: And here go on at length in a longer caption.
| Name | Favorite Number |
|--+-|
| Sue | 42 |
| Tom | 99 |
,#+label: table2
,#+caption[This is table2]: But *with* /this/ table, the /short/ caption is
*lost*.
| Name | Favorite Color |
|---+|
| Alice | Red|
| Bob | Also Red |
,#+label: table3
,#+caption[This is table3]: No org markup is used in this long caption, but
some $\LaTeX$ is!
| Number | Favorite Person |
|+-|
| 0 | Zed |
| 1 | Solo|
#+end_src
When I export it as a LaTeX file, the captions are:
#+begin_src latex
\caption[This is table1]{\label{table1}And here go on at length in a longer
caption.}
#+end_src
#+begin_src latex
\caption[\textbf{lost}]{\label{table2}But \textbf{with} \emph{this} table, the
\emph{short} caption is \textbf{lost}.}
#+end_src
and
#+begin_src latex
\caption{\label{table3}No org markup is used in this long caption, but some
\(\LaTeX\) is!}
#+end_src
The first matches my expectations. The second is an example of taking the last
bit of markup as the short caption. The third seems to lose the short caption
altogether.
When I look at
#+begin_src emacs-lisp
(org-element-map
(org-element-parse-buffer)
'table
(lambda (x) (org-element-property :caption x)))
#+end_src
Only the first caption seems to have the short caption in the parse results at
all. Is this a bug, or should I avoid using markup in captions?
Thank you,
Anthony
#+begin_src emacs-lisp
(org-version)
#+end_src
#+RESULTS:
: 9.3
Re: what happened to org-man?
Hi Tyler, Tyler Smith writes: > > What happend to org-man? I think the file was deleted from org mode, but > I don't see any explanation in the news file. I think this qualifies as > an incompatible change, at least for those of us that used org-man? The prefix for all the link-related libraries was changed from "org-" to "ol-" in v9.3, specifically 499c0a50c (Prefix link-related libraries filenames with "ol", 2019-03-02).
what happened to org-man?
Hi, What happend to org-man? I think the file was deleted from org mode, but I don't see any explanation in the news file. I think this qualifies as an incompatible change, at least for those of us that used org-man? Best, Tyler -- Tyler Smith http://plantarum.ca
Re: Powershell scripting with org-babel
> Micro$loth WindBlows is a computer virus
Well that's mature and appropriate.
I recently did an implementation of `ob-pwsh` for supporting powershell
core (it assumes there’s a pwsh command available on PATH though thats
configurable with `org-babel-command:pws`). Here’s the link
https://github.com/togakangaroo/ob-pwsh. Instructions for installing are in
the README
It works ok and even supports variables but was a 3 hour hack job, plenty
of features missing. I hadn’t even announced it on this list before. The
code is pretty small though - under 60 loc if you want to contribute to it,
I’m game.
I also saw this a while ago but haven’t really dug in
https://old.reddit.com/r/emacs/comments/dkz0n1/babel_with_powershell/?st=k5jqc8es=b464c181
Oh, and powershell is awesome. It’s 2020, we *should* have a runtime in our
terminal (eshell somewhat does this and is pretty good because of it). One
of the things that would be really nice to do some day would be some sort
of conversion between powershell and lisp structures so that we could pass
structured data as hashes and lists between languages - not just strings.
On Mon, Feb 10, 2020 at 7:59 PM briangpowell .
wrote:
> Micro$loth WindBlows is a computer virus
>
> But if you must use Windows, suggest you use Cygwin and BASH and/or EShell
> {the Emacs Shell}--you can do much more than PowerSh3ll
>
> And Emacs & OrgMode work very nicely on Cygwin
>
> On Mon, Feb 10, 2020 at 11:58 AM MS Window
> wrote:
>
>> Hello,
>>
>> can you help me ? I want to use org-babel for Powershell scripting. I
>> found this code chunk on the internet for customizing org-babel for
>> Powershell on github:
>>
>> https://gist.github.com/cbilson/ae0d90d163be4d769f8a15ddb58292bc
>>
>> There is no explanation there I should put the configuration. The
>> org-babel documentation is too brief for me as beginner to understand.
>>
>> Yours sincerely
>>
>> Claus Keller
>>
>>
>>
>>
Re: Powershell scripting with org-babel
Hi Klaus, MS Window writes: > There is no explanation there I should put the configuration. The org-babel > documentation is too brief for me as beginner to understand. First, save that file somewhere. Then, in your emacs config, add the directory containing ob-powershell.el to the `load-path' variable using the function `add-to-list' [0]. Then, load ob-powershell using `require'. Finally, add powershell to `org-babel-load-languages' [1]. Then you should be able to execute powershell babel blocks. Hope that helps, Jack [0] https://www.emacswiki.org/emacs/LoadPath [1] https://orgmode.org/worg/org-contrib/babel/languages.html#configure
Re: Powershell scripting with org-babel
Micro$loth WindBlows is a computer virus
But if you must use Windows, suggest you use Cygwin and BASH and/or EShell
{the Emacs Shell}--you can do much more than PowerSh3ll
And Emacs & OrgMode work very nicely on Cygwin
On Mon, Feb 10, 2020 at 11:58 AM MS Window wrote:
> Hello,
>
> can you help me ? I want to use org-babel for Powershell scripting. I
> found this code chunk on the internet for customizing org-babel for
> Powershell on github:
>
> https://gist.github.com/cbilson/ae0d90d163be4d769f8a15ddb58292bc
>
> There is no explanation there I should put the configuration. The
> org-babel documentation is too brief for me as beginner to understand.
>
> Yours sincerely
>
> Claus Keller
>
>
>
>
Re: Bug: SPC no longer works as a custom agenda key [9.3.4 (9.3.4-elpaplus @ /home/lin/.emacs.d/elpa/26.3/develop/org-plus-contrib-20200206/)]
Hi Yuan Lin, thanks for reporting this. Yes, this is because of the recent addition you are referring to, which I find a bit problematic, even though I understand the intent. It is good to be able to navigate the agenda commands dispatch window but losing the SPC key is too high a price for this. I have pushed a change that advertize the use of C-v and M-v to scroll up and down in export/agenda/attach dispatch buffers, while SPC and DEL are still usable for the export dispatch buffer. >From latest master, you can reuse SPC as a key binding for a custom agenda command. Thanks for reporting this, -- Bastien
Re: org-adapt-indentation default should be nil [legibility 3/6]
On 2/10/20, Bastien wrote: > Hi Samuel, > > thanks for your feedback. > > Samuel Wales writes: > >> obviously, as a default not indenting text as you seem to propose is >> good for newcomers. that statement was in the context of accessibility. > > Perhaps, we will see! indeed we will get opinions.
Re: [ANN/RFC] org-ql-view-dispatch command
Hi Adam, Adam Porter writes: > I've pushed a new feature to org-ql's master branch: a Magit-like view > dispatcher using Jonas Bernoulli's transient.el library. It looks really neat! I wish we could unify at the two main Org dispatch screens, i.e. org export and org capture selection interfaces. Transient is not in Emacs, so we cannot use it by default in Org but would anyone try to provide a transient interface for Org export and capture interfaces? -- Bastien
Re: Prose with markup needs more line spacing [legibility 5/6]
Samuel Wales writes: > nil has always worked for me. i didn't think a new feature was > necessary, but i am curious. what does your change do? (See the other message I just sent for a quick explanation.) -- Bastien
Re: org-adapt-indentation default should be nil [legibility 3/6]
Hi Samuel, thanks for your feedback. Samuel Wales writes: > obviously, as a default not indenting text as you seem to propose is > good for newcomers. Perhaps, we will see! > as for org as it is now, with a mixture of at least 3 indentation > styles in the wild, idk. What I observed is that some users will turn M-x org-indent RET just to have planning lines displayed correctly (i.e. visually indented), while still willing to let the subtree text not indented at all. You can now have this without running org-indent, which I think is an improvement - we'll see. Best, -- Bastien
Re: Fixed vs variable pitch font [legibility 4/6]
i think this is a really good idea. there are subtleties including: - list bullets (fixed is good for aligning succeeding lines) - timestamps (many align these informally or in headers) - numbers (many align these informally -- but .,-+'?) - todo kw (defined by user, would be fantastic to be variable, but some users do such things as making them be 4 characters and aligning them in sibling headers; i think the org main page does this) - table subtleties - agenda subject lines (requires a change in org itself that makes headers and tags individually definable faces so rhs is by default variable but settable not to be, perhaps as part of a change making columns in agenda individually definable for non-pitch reasons) On 2/10/20, Bastien wrote: > Adam Porter writes: > >> Having said that, if Org could have a simple org-mixed-pitch-mode, or >> something like that, that could be very helpful, since it could make >> such configuration much easier. > > If anyone wants to start coding something like this, we can consider > referencing it on Worg. > > -- > Bastien > > -- The Kafka Pandemic What is misopathy? https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
Re: org-adapt-indentation default should be nil [legibility 3/6]
[this is addressed to bastien] hi, if you are thinking of changing the default to indenting meta lines and asking for opinions on that: fwiw, if org /were starting out/, i would propose that meta stuff not be indented at all either. then the regexps everywhere could be reliable. and it reduces number of things to think about. keyboard macros, grep, third party tools in and outside of emacs. the idea being keep to the basics so there will be no surprises. i have a case i won't go into where a tool cannot reliably parse such lines, because it has to distinguish semantic indentation and physical aesthetic indentation. this can't be done without ai in its context. so the tool /outlaws/ physical indentation for a feature. it doesn't actually shoot you or post wanted signs if you physically indent, but the feature will not work. imo there are more arguments too. for example, state change lines and notes can be wide. for accessibility, i always want the default to be the one that does not affect whose who need it, who already have too much to deal with. this is my opinion. obviously, as a default not indenting text as you seem to propose is good for newcomers. as for org as it is now, with a mixture of at least 3 indentation styles in the wild, idk. fwiw.
Re: Prose with markup needs more line spacing [legibility 5/6]
hi bastien, i deeply apologize. that statement was not clear. as much as possible i will be more clear in the future. i appreciate your looking into it. nil has always worked for me. i didn't think a new feature was necessary, but i am curious. what does your change do? samuel
Re: Faster version of org-find-olp
Bastien writes: > Hi Eric, > > Eric Abrahamsen writes: > >> I ended up writing a function on top of that that does find-or-create, >> so you can go to a certain outline path, creating and inserting >> (optionally in sorted order) the missing segments as you go. It was >> fairly difficult to get right, so perhaps it will be of use to someone, >> or appropriate for Worg or even Org proper: >> >> https://github.com/girzel/timesheet.el/blob/master/timesheet.el#L250 > > thanks for this - don't hesitate to reference it somewhere on Worg if > you think that's useful. > > If you think this should go to Org's core, please make a patch and > tell what's the difference with your patch and how to test it to make > sure we really understand the issue at stake. I don't have any issue > with the current implementation of `org-find-olp' so I cannot really > know. It isn't a replacement for `org-find-olp'! It's just built on top of it. `org-find-olp' signals an error if the full path isn't found. My function looks for that error and creates the missing segments of the path. If `org-find-olp' is the equivalent of "cd" in the shell, this function is like "mkdir -p", plus the "cd" afterwards. It's nice for programmatically creating outline structures (ie can be used to create date trees and the like). I guess I think worg is sufficient -- it's a nice utility, but perhaps not necessary for core. Eric
Powershell scripting with org-babel
Hello, can you help me ? I want to use org-babel for Powershell scripting. I found this code chunk on the internet for customizing org-babel for Powershell on github: https://gist.github.com/cbilson/ae0d90d163be4d769f8a15ddb58292bc There is no explanation there I should put the configuration. The org-babel documentation is too brief for me as beginner to understand. Yours sincerely Claus Keller
[ANN/RFC] org-ql-view-dispatch command
Hi friends, I've pushed a new feature to org-ql's master branch: a Magit-like view dispatcher using Jonas Bernoulli's transient.el library. It makes for quick and easy modification of org-ql-view queries, allowing you to build them interactively rather than requiring you to write Lisp code or use the Customization system. Here's a screencast of it: https://github.com/alphapapa/org-ql/raw/master/images/org-ql-view-dispatch.gif It seems to work well, but I'd appreciate any feedback. Thanks, Adam
Bug: SPC no longer works as a custom agenda key [9.3.4 (9.3.4-elpaplus @ /home/lin/.emacs.d/elpa/26.3/develop/org-plus-contrib-20200206/)]
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.
My org-agenda-custom-commands contains
(" " "Notes" tags "NOTE"
((org-agenda-overriding-header "Notes")
(org-tags-match-list-sublevels t)))
notice the key is "SPC" in this case, it used to work without issue. however
after a recent update of spacemacs and package update
(org-plus-contrib-20191230). It suddenly stopped working.
And in the later version I also tried -20200206, it is still broken.
This issue is initially reported to spacemacs
as issue 13138 - SPC no longer
works as a custom agenda command key in org-mode
, after some
investigation, it it highly possible that here I quote:
A possible reason why the behavior changed might be because of this commit
from 2 months ago:
https://code.orgmode.org/bzg/org-mode/commit/80b29acba3847c1756fa3c143d6991964f7273ca
agenda: Enable navigation for the agenda dispatch buffer
- lisp/org-agenda.el (org-agenda-get-restriction-and-command): Use
keys C-n, C-p, SPC, DEL analogue to export dispatcher. See function
org-export--dispatch-action.
Reported by Nathan Neff
https://lists.gnu.org/archive/html/emacs-orgmode/2019-10/msg00179.html.
Could those agenda navigation keys made configurable? Or an option to
disable the newly introduced navigation if not needed?
Best Regards,
Yuan
Emacs : GNU Emacs 26.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10)
of 2019-08-29
Package: Org mode version 9.3.4 (9.3.4-elpaplus @
/home/lin/.emacs.d/elpa/26.3/develop/org-plus-contrib-20200206/)
[BUG?] org-babel-lilypond-commands can't be set through customize
Hi! In ob-lilypond the variable org-babel-lilypond-commands appears to be in a weird state. The customize interface says: org-babel-lilypond-commands: nil > [ State ]: UNKNOWN, you should not see this. > Commands to run lilypond and view or play the results. > These should be executables that take a filename as > an argument. > On some system it is possible to specify the filename > directly > and the viewer or player will be determined from the file > type; > you can leave the string empty on this case. [C-h v] says: org-babel-lilypond-commands is a variable defined in ‘ob-lilypond.el’. It is void as a variable. I can't set the variable through customize. I don't know what the syntax would be to set it with setq. Actually I only need to customize the more specific org-babel-lilypond-midi-command. I can set this one with something like (setq org-babel-lilypond-midi-command "timidiy"). However its docstring says: org-babel-lilypond-midi-command is a variable defined in ‘ob-lilypond.el’. Its value is "timidity" This variable may be risky if used as a file-local variable. Documentation: Command to play a MIDI file on your system. Do not set it directly. Customize ‘org-babel-lilypond-commands’ instead. Hence my attempt to customize org-babel-lilypond-commands. I have org-mode 9.3.1. Regards, Victor
Re: org-babel-load-file support elisp
>> The problem now is that removing support for 'elisp' would break too >> much. > > What I suggest for this particular issue is this: first be liberal > while staying consistent (thus allowing "elisp" as Troy suggest), > then be strict when a major release is issued (thus removing aliases > that are problematic, not just "elisp" but others.) > > WDYT? Troy, would you be able to prepare a patch for this? My 2¢ from the peanut gallery. Generally speaking, I’m in favor of consistency. A couple of months ago, I stumbled over the fact that ‘elisp’ seemed to do syntax highlighting correctly but didn’t tangle. I didn’t, at the time, work out the cause of the problem, I just learned to use ‘emacs-lisp’ as the language name. Looking at this thread, it seems like there are a bunch of exceptions to the rule that the language is be the name of the mode without ‘-mode’. Just off the top of my head, I can think of several languages supported by multiple modes. If the rule is that the language is the mode name, then if I use ‘extra-special-language-mode’ to edit ‘language’, do I have to use ‘extra-special-language’ as the language name? Is that going to seem natural? What burden does that put on the developer of ‘extra-special-language-mode’ to make tangle and other Org-mode features work like they would for ‘language-mode’? I wonder if it makes more sense to invent a mechanism for assigning language synonyms that can be used throughout Org? Be seeing you, norm P.S. Just to prove I can play devil’s advocate, I’m very conscious of the fact that a few days ago, I invented an ‘xproc-mode’ as a vacuous extension to ‘xml-mode’ precisely *because* I wanted to define different org-babel-execute behavior. -- Norman Tovey-Walsh | Some disguised deceits https://nwalsh.com/ | counterfeit truth so perfectly | that not to be taken in by them | would be an error of | judgment.--La Rochefoucauld signature.asc Description: PGP signature
