Hi,
We're highly unlikely to feel in our life the strange need to know the
verse number at point within a verse block (verse numbers are not equal
to line numbers).
However, in my translation of Homer's Odyssey (work in progress), I
often need to get (at point) both the verse number and the book
Hello,
I need to extract a column from a table to use as input to a source
block. I want the extracted column to be returned as a column but it is
returned as a row. The following illustrates the problem:
#+name: s1
| scale | scale1 | scale3 | jid |
| - | 1.00402 | 0.952329 | 1632 |
| -
Roger,
> Is there some means of changing 'data=s1[,3]' to accomplish this?
there may be some more formal way (and i think some of the
data.frame.alternative packages, like data.table:: or dplyr::, have
their own ways), but you might try transposing
> t(data=s1[,3])
cheers, Greg
Hi Roger,
It's a dirty solution, but you can try:
#+name: s1
| scale | scale1 | scale3 | jid |
| - | 1.00402 | 0.952329 | 1632 |
| - | 1.00402 | 0.962247 | 1633 |
#+begin_src emacs-lisp :var data=s1 col=3
(let* ((column (mapcar (lambda (r) (format "%s" (nth col r))) data)))
Hello John & co.,
I need to chime in when it comes to the UI:
On Thursday, 12 Aug 2021 at 13:19, John Kitchin wrote:
> I would say the UI that I like, have used for many years, and is the
> default of org-ref is:
>
> 1. You type C-c ] to insert a citation
> 2. You type C-u C-c ] to insert a cross
Hello Greg,
Greg Minshall writes:
> Roger,
>
>> Is there some means of changing 'data=s1[,3]' to accomplish this?
>
> there may be some more formal way (and i think some of the
> data.frame.alternative packages, like data.table:: or dplyr::, have
> their own ways), but you might try transposing
>
Hello Juan,
Juan Manuel Macías writes:
> #+name: s1
> | scale | scale1 | scale3 | jid |
> | - | 1.00402 | 0.952329 | 1632 |
> | - | 1.00402 | 0.962247 | 1633 |
>
> #+begin_src emacs-lisp :var data=s1 col=3
> (let* ((column (mapcar (lambda (r) (format "%s" (nth col r))) data)))
>
Hello Roger,
Roger Mason writes:
> Thank you, I think I may be able to get this to work.
You're welcome. Just a minor fix: although the code works fine,
naturally the asterisk in `let' was unnecessary. This is a new version
with the code explained, in case you find it useful:
#+begin_src emacs-
Hello,
I think this might be more of a git question than an Org question, but I
imagine I might find the answer here and that it might be useful to others, so
I ask here.
I'd like to keep derivative products (the LaTeX output, the final PDF, etc.)
available in Git, but not commit those changes
> > t(data=s1[,3])
(sorry, i thought we were in R-land... :(
Hello,
I'm already registered at the Emacs Savannah group with access to the
org-mode repository, but it seems to be a month behind
https://code.orgmode.org/bzg/org-mode.
I'm new and I don't have an account on code.orgmode.org, but I'm ready to
submit a new version of ob-julia.el. Should I wait f
Hi Ken,
Ken Mankoff writes:
> I'd like to keep derivative products (the LaTeX output, the final PDF,
> etc.) available in Git, but not commit those changes each time I
> change the Org file. Perhaps git-annex as appropriate for this, but
> seems over-kill.
>
> Is there some way to mostly-seamless
Hi,
I want an `org-id / :ID:` publishing workflow.
To eliminate "xy-case" I first describe what I've been trying to do.
First I've added an `:ID:` to many headlines through `M-x org-id-get-create`.
Then I've added one `#+INDEX: word` under one of those headlines.
Then I've executed that (I do
I just created this function for copying the thing under the cursor (it
works for some #+BEGIN blocks and links). I think it would be useful for
others, so I'm creating this post for getting feedback on the Elisp code
and sharing it to those interested.
#+BEGIN_SRC elisp
(defun my/org-kill-thing
Hi Rodrigo,
Thanks for sharing, it seems interesting and useful. But I think this
function is missing in your post: `my/kill-new'.
Best regards,
Juan Manuel
Rodrigo Morales writes:
> I just created this function for copying the thing under the cursor (it
> works for some #+BEGIN blocks and li
* The question
Let's say I have the following link
#+BEGIN_SRC org
This is a sentence [[foo][bar]]. This is another sentence.
#+END_SRC
How to programmatically get the description of the link (i.e. =bar=)?
* Additional information
I've tried using =org-element-context=. The following sexp wa
I think you can do something like this:
(defun get-description ()
(interactive)
(let ((link (org-element-context)))
(message (buffer-substring (org-element-property :contents-begin link)
(org-element-property :contents-end link)
John
---
Professo
Ken Mankoff writes:
> Hello,
>
> I think this might be more of a git question than an Org question, but I
> imagine
> I might find the answer here and that it might be useful to others, so I ask
> here.
>
> I'd like to keep derivative products (the LaTeX output, the final PDF, etc.)
> availabl
Just adding one element. When I open `theindex.inc` in emacs, then do `M-x
org-mode`, then go on one of the links and do `M-x org-open-at-point`, the
link is correctly followed.
But when exported to html, the link from `theindex.html` is broken, because no
target has been actually created usin
Ken,
You could consider using git-lfs, Large File Support. There is some setup and
then you can say track *.pdf and that will tell git to track the binary file in
a more efficient way. I use this mailing for csv files that I want to have a
snapshot version of with the Jupyter notebook that used
I've written the following function for retrieving the links from a
given Org Mode buffer.
#+BEGIN_SRC elisp
(defun my/org-collect-links-in-buffer (buffer)
"Collect all the links in the current buffer. If the link has a
description, then it is also collected.
Returns a list of PLISTS of the f
Rodrigo Morales writes:
> (t
>(error "The element at point couldn't be copied.")))
I would fall back to region between :begin and :end of the element.
Also, it might be helpful to print a short message about what element
have just been copied.
Best,
Ihor
> On Aug 13, 2021, at 6:54 PM, Mark Barton wrote:
>
> Ken,
>
> You could consider using git-lfs, Large File Support. There is some setup and
> then you can say track *.pdf and that will tell git to track the binary file
> in a more efficient way. I use this mailing for csv files that I wan
> On Aug 13, 2021, at 7:53 PM, Rob Sargent wrote:
>
>
>
>> On Aug 13, 2021, at 6:54 PM, Mark Barton wrote:
>>
>> Ken,
>>
>> You could consider using git-lfs, Large File Support. There is some setup
>> and then you can say track *.pdf and that will tell git to track the binary
>> file i
I cannot have the following minimal example working consistently:
$ cat hello.org
* hello
:PROPERTIES:
:ID: e54113f9-2ad7-4a86-94be-68ffc696de0b
:END:
#+INDEX: hello-keyword
#+begin_src emacs-lisp
(org-id-update-id-locations '("hello.org" "bye.org" "theindex.org"))
#+end_
it is an interesting question as many things go into the product:
- org file
- your .el files
- org version
- emacs version
- os
- hw
- export commands run
so the desire to keep the product is understandable. not only is it
effort to find the export commands run, but other stuff might change
out
26 matches
Mail list logo
