Re: :session for Julia in org babel?
On Saturday, 20 Aug 2022 at 13:56, Ihor Radchenko wrote: > Sure. You can submit the patch here, and I will apply it. Here it is. Thank you. -- : Eric S Fraga, with org release_9.5.4-737-gd3a9c4 in Emacs 29.0.50 From 2564c84b41de55d478ba249fa932c40ac62fe510 Mon Sep 17 00:00:00 2001 From: Eric S Fraga Date: Mon, 22 Aug 2022 10:27:52 +0100 Subject: [PATCH] org-contrib/babel/languages/ob-doc-julia.org: Sessions requirements * ob-doc-julia.org (Requirements, Sessions): Specify the extra Julia packages required for sessions to work. --- org-contrib/babel/languages/ob-doc-julia.org | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/org-contrib/babel/languages/ob-doc-julia.org b/org-contrib/babel/languages/ob-doc-julia.org index 970f9232..65ba49b0 100644 --- a/org-contrib/babel/languages/ob-doc-julia.org +++ b/org-contrib/babel/languages/ob-doc-julia.org @@ -47,7 +47,7 @@ The documentation for Julia describes it as "a flexible dynamic language, approp Julia code blocks can be used in Org to define functions, filter and analyze data, create graphics and figures, and produce reproducible research papers. * Requirements and Setup -Julia code blocks in Org require a working Julia installation. Julia is [[https://julialang.org/downloads/][available]] for FreeBSD on ARM, Linux on ARM or x86, macOS on ARM or x86, and Windows. +Julia code blocks in Org require a working Julia installation. Julia is [[https://julialang.org/downloads/][available]] for FreeBSD on ARM, Linux on ARM or x86, macOS on ARM or x86, and Windows. See [[sessions][below]] for further requirements for sessions with Julia. There is [[https://github.com/JuliaEditorSupport/julia-emacs][julia-mode]] in Melpa for Emacs. It requires [[https://ess.r-project.org/][Emacs Speaks Statistics]] (ESS). @@ -67,8 +67,8 @@ Org mode can be configured to use Julia by creating an entry for it in =org-babe Babel support for Julia defines two Julia-specific header arguments, =:width= and =:horizontal=. -** Sessions -Sessions are fully supported through ESS. +** Sessions <> +Sessions are fully supported through ESS. Two Julia packages must be added to the Julia configuration to enable sessions to work: [[https://github.com/JuliaData/DataFrames.jl][DataFrames]] and [[https://github.com/JuliaData/CSV.jl][CSV]]. Sessions can be used to define functions, set up variables, and share code between source blocks. * Examples of Use -- 2.30.2
Updating Emacs
Dear all, I currently use Emacs 27.2 (9.0) and need to update to the last version. No idea how my current Emacs was installed on my Mac. In case this helps, when I do on Terminal: § which -a- emacs /usr/local/bin/emacs /opt/local/bin/emacs /usr/local/bin/emacs What would the way to go to update my emacs to the last version without affecting any of my configuration or packages? Thanks! G.
Re: Updating Emacs
Gerardo Moro @ 2022-08-22 13:31 : > Dear all, Hi! 🙃 > I currently use Emacs 27.2 (9.0) and need to update to the last version. > No idea how my current Emacs was installed on my Mac. You probably installed it via brew. https://brew.sh > In case this helps, when I do on Terminal: > > § which -a- emacs > > /usr/local/bin/emacs > /opt/local/bin/emacs > /usr/local/bin/emacs > > What would the way to go to update my emacs to the last version without > affecting any of my configuration or packages? I would install railwaycat as it's built with mac stuff in mind (such as trackpad zoom, mac modifier keys, etc...) https://github.com/railwaycat/homebrew-emacsmacport It's installed via brew as well and works very nicely. It'll upgrade you to 28.1 and should be fairly painless. Note: You'll probably have paths to it such as: /opt/homebrew/Cellar/emacs-mac/emacs-28.1-mac-9.0 and /opt/homebrew/Cellar/emacs-mac/emacs-28.1-mac-9.0/share/emacs/28.1/etc/ Note that /opt is for M1 macs only. If you have an Intel, it will be in /usr, I think. It won't be hard to find as it sets it up for you and outputs stuff in the terminal which you should copy/paste into a note to make sure you remember it (and debug if there are any problems). I hope this helps! One more thing to note: I'm pretty new to it all, I've only been doing it for a couple of months, but I figured I would reply and see if I can help from my own experience. Also, I literally write everything down in notes (using Prot's denote) so that I don't forget stuff like this. 🙃 > Thanks! > G. Summer. P.S. If you're just using terminal on a Mac, that's fine, but I would check out iTerm 2 (completely free and amazing): https://iterm2.com -- Summer, Sent from MU4E in Emacs, Because I'm becoming a NEWBIE at this!
Re: [PATCH] org-manual: Document `org-babel-default-inline-header-args'
Ihor Radchenko writes: > In https://orgmode.org/list/87ee927emf.fsf@localhost I proposed to > document org-babel-default-inline-header-args in the manual. > > Here is the patch. Applied onto main via 1b5ccb109. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=1b5ccb10971f67c7f80052ddb32b5e5cf2dba71d -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [PATCH] org-babel: Do not echo output of resolved noweb references
Ihor Radchenko writes: > Currently, every time Org resolves noweb references, the behaviour is > resembling :results silent. That is, the results of evaluation are > displayed, but not inserted after the executed source blocks. > > I propose to change this by using :results none that will display > "results silenced" echo instead of messaging the whole result string. Applied onto main via 2dfdc8953. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2dfdc895351dd867042a4693a63cc688a7be1fb5 -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [PATCH] org-fast-tag-selection: Make group tags separator not break alignment
Ihor Radchenko writes: > Subject: [PATCH] org-fast-tag-selection: Make group tags separator not break > alignment Applied onto main via 090dacb0a. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=090dacb0a9a3aac02b8cfa0e25f607d1f3cd2064 -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [Feature Request] Create an org-md-toplevel-hlevel variable to allow users to set the level of top level headings in markdown export
On 21/08/2022 22:11, Rohit Patnaik wrote: Since md backend is derived from html, is it necessary to define an option specific to markdown or the value defined for HTML may be reused? I am unsure which variant will be more convenient, so it is not more than an idea that may be easily discarded. I considered reusing the value from the HTML exporter, but I rejected it, because the org-html-toplevel-hlevel defaults to 2. Reusing it would alter the existing default behavior for markdown exports, which I thought was undesirable. Thank you for clarification. I forgot that MarkDown has metadata block, while for HTML document title is the only option is . Of course, changing default is not an option and org-md-toplevel-hlevel is better.
Re: [PATCH] org-export: Make results of named code blocks a valid link
Ihor Radchenko writes: >> Or just carry it over for :exports results only? > > I like this idea better. See the attached patch. > After the patch, links to :exports both blocks will be ambiguous, unless > the results are explicitly named. So, I documented this detail in the > manual. Applied onto main via 5184c4382. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5184c4382da171fe5f451694251a0e28c24f4d98 -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: Suspected bug: '#+STARTUP: indent' messes up inlinetasks' tag alignment
alain.coch...@unistra.fr writes: > > Applying patches is out of scope of the manual. > > Fair enough, but in that case shouldn't the word "patches" be removed > from "Bug reports, ideas, patches, etc."? The word "patches" refers to sending patches, not applying or testing. It only makes sense for people who know how to create patches. In addition, we have https://orgmode.org/worg/org-contribute.html detailing how to propose patches to Org. On the other hand, testing the proposed patches is also a kind of Feedback and can be thought as fitting to the manual section. > > Next time, you can just ask to provide an alternative way of testing. I > > can then just upload the patched version to an alternative repository. > > Well, I was trying to save you some time so that you can spend it on > more constructive actions. I succeeded, and learned things in the > process -- patching (at least basic concepts and actions) is > relatively simple, so I think it could easily be _within_ the scope of > the manual. It might. It is probably even useful. Would you mind writing several paragraphs for the manual about applying patches? -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: :session for Julia in org babel?
"Fraga, Eric" writes: > On Saturday, 20 Aug 2022 at 13:56, Ihor Radchenko wrote: >> Sure. You can submit the patch here, and I will apply it. > > Here it is. Thank you. Thanks! Applied onto master via 56fd0591. https://git.sr.ht/~bzg/worg/commit/56fd0591eed333771ddf7ab522bf8da2c2b4bd7b -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [PATCH] org-manual.org: Update links to MathJax docs
On 22/08/2022 09:39, Ihor Radchenko wrote: Max Nikulin writes: Hmm. I actually missed that 302 it is not actual error. Applied onto main via 8d93f9b6b. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=8d93f9b6b4e15427d62b84013ee726a0e6760ad9 Let's try to convince Woof! that it is really Applied
applying patches
On 22/08/2022 19:08, Ihor Radchenko wrote: alain.coch...@unistra.fr writes: Well, I was trying to save you some time so that you can spend it on more constructive actions. I succeeded, and learned things in the process -- patching (at least basic concepts and actions) is relatively simple, so I think it could easily be _within_ the scope of the manual. It might. It is probably even useful. Would you mind writing several paragraphs for the manual about applying patches? It may be enough to add links to already written documents. For those who are familiar with git: https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project Perhaps I have seen better introduction how to use the "patch" command than https://www.gnu.org/software/diffutils/manual/html_node/Merging-with-patch.html
Re: Auto-checking dead links in the manual (was: http: links in the manual)
On 22/08/2022 09:46, Ihor Radchenko wrote: Juan Manuel Macías writes: Maybe, instead of repairing the links manually, we could think of some code that would do this work periodically, and also check the health of the links, running a url request on each link and returning a list of broken links. I don't know if it is possible to do something like that in Elisp, as I don't have much experience with web and link issues. I think there are also external tools, like Selenium Web Driver, but my experience with it is very limited (I use Selenium from time to time when I want to take a screenshot of a web page). This is a good idea. Selenium is probably an overkill since we should better not link JS-only websites from the manual anyway. What we can do instead is a make target that will use something like wget. Patches are welcome! I hope that selenium is currently overkill, however more sites are starting to use anti-DDOS shields like cloudflare and HTTP client may be banned just because it does not fetch other resources like JS scripts. I do not have a patch, just an idea: export backend that ignores everything besides link and either send requests from lisp code or generate file for another tool. #+attr_linklint: ... may be used to specify regexp that target page is expected to contain. There are some complications like e.g. "info:" links having special code to generate HTML with URL derived from original path. So it may be more robust to parse HTML document (without checking of linked document text).
Re: [QUESTION] How to specific image size attributes under headline scope?
Hi Christopher, >>> I want to specify image size under headline properties. Is it possible to do >>> this? >> >> As I understand org.el, this is solely governed by >> `org-display-inline-image–width’, which only looks at `#+attr_*’ keywords >> when >> setting an image width. >> >> All the best, >> Timothy > > Yes, what about letting org-mode support headline level image size > specification? > Is this a good idea and easy to implement? Hmm, so would this basically be setting all images within a certain section to inherit a different `org-image-actual-width' / `org-latex-image-default-width' parameter? All the best, Timothy
Best way to capture state change times that are *not* now?
'C-u C-c C-t' forces a log note to be included with the state change, but the state change log note is always *now* (CMIIAW). Is there a way to change the state on a todo and have it ask for a date/time to go with the state change? Reason: I often don't get to change todo' state to DONE until long after it was done. I'd like to set the date/time to when it really happened. -- David Masterson
org-mode compile issue this morning - how to report this?
Hello,
This morning I can't get org-mode to compile and load at all. And the
bug reporting is not working.
What to do?
Thank you!
Here are this morning's messages:
make -C lisp compile
make[1]: Entering directory '/home/dortmann/src/git-org-mode/lisp'
rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc
org-install.elc
org-version: 9.5.4 (release_9.5.4-756-g090dac)
Loading /home/dortmann/src/git-org-mode/lisp/org-compat.el (source)...
Error: error ("Eager macro-expansion failure: (void-function
byte-compile-warn-obsolete)")
mapbacktrace(#f(compiled-function (evald func args flags) #-0x9324d572c510f29>))
debug-early-backtrace()
debug-early(error (error "Eager macro-expansion failure:
(void-function byte-compile-warn-obsolete)"))
signal(error ("Eager macro-expansion failure: (void-function
byte-compile-warn-obsolete)"))
error("Eager macro-expansion failure: %S" (void-function
byte-compile-warn-obsolete))
internal-macroexpand-for-load((defalias 'org-string-width #'(lambda
(string &optional pixels) "Return width of STRING when displayed in the
current buffer.\nReturn width in pixels when PIXELS is non-nil." (if
(and (version< emacs-version "28") (not pixels)) (org--string-width-1
string) (remove-text-properties 0 (length string) '(wrap-prefix t
line-prefix t) string) (unless pixels (remove-text-properties 0 (length
string) '(face t) string)) (let ((current-invisibility-spec (or (and
(not (listp buffer-invisibility-spec)) buffer-invisibility-spec) (let
(result) (dolist (el buffer-invisibility-spec) (unless (or (memq el
'(org-fold-drawer org-fold-block org-fold-outline)) (and (listp el)
(memq (car el) '(org-fold-drawer org-fold-block org-fold-outline
(push el result))) result))) (current-char-property-alias-alist
char-property-alias-alist)) (with-temp-buffer (setq-local
display-line-numbers nil) (setq-local buffer-invisibility-spec (if
(listp current-invisibility-spec) (mapcar (lambda (el) (if (and (consp
el) (cdr el)) (list (car el)) el)) current-invisibility-spec)
current-invisibility-spec)) (setq-local char-property-alias-alist
current-char-property-alias-alist) (let (pixel-width symbol-width)
(with-silent-modifications (setf (buffer-string) string) (setq
pixel-width (if (get-buffer-window (current-buffer)) (car
(window-text-pixel-size nil (line-beginning-position) (point-max)))
(set-window-buffer nil (current-buffer)) (car (window-text-pixel-size
nil (line-beginning-position) (point-max) (unless pixels (setf
(buffer-string) "a") (setq symbol-width (if (get-buffer-window
(current-buffer)) (car (window-text-pixel-size nil
(line-beginning-position) (point-max))) (set-window-buffer nil
(current-buffer)) (car (window-text-pixel-size nil
(line-beginning-position) (point-max))) (if pixels pixel-width (/
pixel-width symbol-width t)
eval-buffer(# nil
"/home/dortmann/src/git-org-mode/lisp/org-macs.el" nil t)
load-with-code-conversion("/home/dortmann/src/git-org-mode/lisp/org-macs.el"
"/home/dortmann/src/git-org-mode/lisp/org-macs.el" nil t)
require(org-macs)
eval-buffer(# nil
"/home/dortmann/src/git-org-mode/lisp/org-compat.el" nil t)
load-with-code-conversion("/home/dortmann/src/git-org-mode/lisp/org-compat.el"
"/home/dortmann/src/git-org-mode/lisp/org-compat.el" nil nil)
load("org-compat.el")
eval((load "org-compat.el") t)
command-line-1(("--eval" "(setq vc-handled-backends nil
org-startup-folded nil org-element-cache-persistent nil)" "--eval"
"(add-to-list 'load-path \".\")" "--eval" "(load \"org-compat.el\")"
"--eval" "(load \"../mk/org-fixup.el\")" "--eval" "(org-make-org-version
\"9.5.4\" \"release_9.5.4-756-g090dac\")"))
command-line()
normal-top-level()
Eager macro-expansion failure: (void-function byte-compile-warn-obsolete)
make[1]: *** [Makefile:72: org-version.el] Error 255
make[1]: Leaving directory '/home/dortmann/src/git-org-mode/lisp'
make: *** [mk/targets.mk:96: compile] Error 2
Re: Auto-checking dead links in the manual (was: http: links in the manual)
> I hope that selenium is currently overkill Me too, although the WebDriver protocol itself is less bloated than Selenium. Personally I use Etaoin[1] for anything WebDriver-related, it's pretty compact, Lisp-y, and you can easily run unit tests with Emacs. As for anything ready-made for cleaning up dead links, I'm not aware of, unfortunately. [1] https://github.com/clj-commons/etaoin
Re: [QUESTION] How to specific image size attributes under headline scope?
Timothy writes: > Hi Christopher, > I want to specify image size under headline properties. Is it possible to do this? >>> >>> As I understand org.el, this is solely governed by >>> `org-display-inline-image–width’, which only looks at `#+attr_*’ keywords >>> when >>> setting an image width. >>> >>> All the best, >>> Timothy >> >> Yes, what about letting org-mode support headline level image size >> specification? >> Is this a good idea and easy to implement? > > Hmm, so would this basically be setting all images within a certain section to > inherit a different `org-image-actual-width' / `org-latex-image-default-width' > parameter? > > All the best, > Timothy Yes, like this: #+begin_src org ,* headline 1 This image will be displayed in 200 width. ,#+ATTR_ORG: :width 200 ,#+ATTR_LATEX: :width 2.0in ,#+ATTR_HTML: :width 200px [[file:kk.png]] This image will be displayed in 600 width, it has no manually specified image size, it will use ~org-image-actual-width~. [[file:kk.png]] ,** headline 2 :PROPERTIES: :IMAGE-WIDTH: 500 :END: This image will be displayed in 200 width. ,#+ATTR_ORG: :width 200 ,#+ATTR_LATEX: :width 2.0in ,#+ATTR_HTML: :width 200px [[file:kk.png]] This image will be displayed in 500 width, it has no manually specified image size, it will use "headline 2" scope property ":IMAGE-WIDTH: 500". This is what I want. (I assume there is a new property which maybe named like :IMAGE-WIDTH:.) [[file:kk.png]] #+end_src -- [ stardiviner ] I try to make every word tell the meaning that I want to express without misunderstanding. Blog: https://stardiviner.github.io/ IRC(libera.chat, freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 signature.asc Description: PGP signature
Re: Best way to capture state change times that are *not* now?
David Masterson writes: > 'C-u C-c C-t' forces a log note to be included with the state change, > but the state change log note is always *now* (CMIIAW). > > Is there a way to change the state on a todo and have it ask for a > date/time to go with the state change? > > Reason: I often don't get to change todo' state to DONE until long after > it was done. I'd like to set the date/time to when it really > happened. Found an acceptable method. Steps: 1. Do the state change 2. Position cursor at end of datetime in the log note 3. Use 'C-c !' to change the datetime -- David Masterson
Re: org-capture and fast selection of tags
Christian, did you get a chance to take a look at my further comments on the patch? -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: org-mode compile issue this morning - how to report this?
Daniel Ortmann writes: > This morning I can't get org-mode to compile and load at all. And the > bug reporting is not working. > > What to do? > > Thank you! > > Here are this morning's messages: > > make -C lisp compile What if you just run "make" from inside the Org repo? What is your Emacs version? -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Update Woof! version at updates.orgmode.org? (was: [PATCH] org-manual.org: Update links to MathJax docs)
Max Nikulin writes: >> Applied onto main via 8d93f9b6b. >> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=8d93f9b6b4e15427d62b84013ee726a0e6760ad9 > > Let's try to convince Woof! that it is really > > Applied Ain't working... Bastien, is there any chance that Woof! version used in updates.orgmode.org can be updated? -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: applying patches
Max Nikulin writes: >> It might. It is probably even useful. Would you mind writing several >> paragraphs for the manual about applying patches? > > It may be enough to add links to already written documents. I'd say that the purpose of describing patch or git apply in the manual is a quick reference for ordinary users who report a bug and want to test the proposed fix. More detailed instructions may be added to https://orgmode.org/worg/org-contribute.html > For those who are familiar with git: > > https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project > > Perhaps I have seen better introduction how to use the "patch" command than > https://www.gnu.org/software/diffutils/manual/html_node/Merging-with-patch.html I'd better see these links in org-contribute. Possibly, we can add a new item to "Ways that do not involve programming": - Help to test the proposed patches: You can help checking the quality of existing patches submitted to the mailing list. Just apply the patch (see [[how to apply patches]]) and try using it with your Org setup. Then report any issues or rough edges. <> can then detail different ways to do it and provide the above links as further reading. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: Auto-checking dead links in the manual (was: http: links in the manual)
Max Nikulin writes: > I hope that selenium is currently overkill, however more sites are > starting to use anti-DDOS shields like cloudflare and HTTP client may be > banned just because it does not fetch other resources like JS scripts. Such links are to be considered dead for the purposes of Org manual. We must not link websites that cannot be opened without running non-free JS. It is according to GNU Documentation Standards. > I do not have a patch, just an idea: export backend that ignores > everything besides link and either send requests from lisp code or > generate file for another tool. > > #+attr_linklint: ... > > may be used to specify regexp that target page is expected to contain. > There are some complications like e.g. "info:" links having special code > to generate HTML with URL derived from original path. So it may be more > robust to parse HTML document (without checking of linked document text). Yes, the most robust way will be simply extracting links from the html version of the manual and testing them using whatever method is appropriate. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
