On Thursday, 6 February 2020 19:23:36 CET Jeremie Juste wrote:
> I've found that some strange results when outputing html from R.
> Do you have some insights on a potential solution?
On my system, org-mode 3.6.1 provides the expected table.
All the best
Hi Dominique,
Dominique Dumont writes:
> On Thursday, 6 February 2020 19:23:36 CET Jeremie Juste wrote:
>> I've found that some strange results when outputing html from R.
>> Do you have some insights on a potential solution?
>
> On my system, org-mode 3.6.1
This seems to be a *very* version of
Hello,
Gustav Wikström writes:
> Hmm, maybe that is so.. Except raw-path is called path (not really an
> issue though) and there is another property called raw-link. Not sure
> how to interpret the use of both path and raw-link. And there are
> things happening between parsing the actual buffer
Hello,
Alan Schmitt writes:
> Thank you for the explanation. Is there a way to either escape the
> parentheses (maybe url-encode them),
*shivers* Please never suggest again url-encoding links in Org! ;) We
only got out of this hell recently. I don't want to dive in again.
> or to automatically
Dominique Dumont writes:
> On my system, org-mode 3.6.1 provides the expected table.
My system produces the expected table as well (org 9.3.2, R 3.6.2).
--Jack
On Friday, 7 February 2020 14:38:53 CET Bastien wrote:
> This seems to be a *very* version of org-mode ;)
Bummer... I remember that I've used org-version to get the version number. I
guess I have cut'n'pasted an unrelated number :-/
For the record, I've tested R and html output on Org mode versi
Hi everyone,
Quick follow up about this: following Eric's suggestion, I came up with the
following block, which cleans up all the cruft from the output of the
=script= command and produces a nicely formatted session transcript:
#+NAME: cleanup
#+BEGIN_SRC emacs-lisp :var data="" :results value :e
On 2020-02-07 15:33, Nicolas Goaziou writes:
> *shivers* Please never suggest again url-encoding links in Org! ;) We
> only got out of this hell recently. I don't want to dive in again.
Sorry, I should have put a smiley there.
> There is some specific syntax in links. More specifically, the
> f
Hi Bastien,
Bastien writes:
>> The variable `org-table-header-line-p' doesn't seem to have any effect
>> for me, I find that I need to call "M-x org-table-header-line-mode" even
>> when it's set.
>
> Should be fixed now.
Confirmed, it works correctly for me now.
>> Also, "M-x org-table-header-
On Friday, 7 Feb 2020 at 16:26, Diego Zamboni wrote:
> Quick follow up about this: following Eric's suggestion, I came up with the
> following block, which cleans up all the cruft from the output of the
> =script= command and produces a nicely formatted session transcript:
You might like to add "
Diego Zamboni writes:
> I came up with the following block, which cleans up all the cruft from
> the output of the =script= command and produces a nicely formatted
> session transcript:
>
> #+NAME: cleanup
> #+BEGIN_SRC emacs-lisp :var data="" :results value :exports none
> (replace-regexp-in-s
Hi Jack,
Jack Kamm writes:
> FWIW, I wouldn't mind if this were a global minor mode, I intend to
> activate it globally with `org-table-header-line-p'.
Well, it only makes sense in org buffers, so activating it through
this variable is okay IMO.
> Since updating and testing for a few minutes,
Hi Stardiviner,
I fixed this in master, thanks for reporting this bug.
Best,
--
Bastien
org-latex-title-command does not honor the document SUBTITLE or %s
substitution, and throws an error invalid format character %s.
Investigation showed that org-latex--format-spec did not have an entry
for %s. Making the ob
Hi Adam and Eric for your further comments!
I had read a bit about the =rx= package but not used it, thanks for the
pointer to =xr=, makes it a lot easier to figure out the syntax.
One more thing I realized is that I can make the desired settings the
defaults within my document, and even automati
I have a need to lay out source blocks side by side, in order to present
before and after changes to the source. If I could embed a block in a
table, that would do it.
Is there another obvious way that I'm missing?
Hilight etc is important, but also actually compiling the code to maintain
correct
Hi,
while org-superstar-mode (a minor mode that prettifies org headlines and
item bullets, see
https://github.com/dw-github-mirror/org-superstar-mode) is awaiting it's
debut on MELPA, I am currently doing a few more touch-ups to ensure
quality. While I am working on providing proper unit tests, I
Hello,
Jack Kamm writes:
> Dominique Dumont writes:
>
>> On my system, org-mode 3.6.1 provides the expected table.
>
> My system produces the expected table as well (org 9.3.2, R 3.6.2).
>
> --Jack
Thanks for the info.
Unfortunately I couldn't identify the issue
I updated R and org (org 9.3.
Hi Jeremie,
> Thanks for the info.
> Unfortunately I couldn't identify the issue
> I updated R and org (org 9.3.2, R 3.6.2).
> but I'm still getting [the error]
Sorry, I missed the initial property line where you set the ":session"
header argument.
When I set the ":session" header argument, I g
Hi Bastien,
Bastien writes:
>> I have noticed a new bug, where the header line randomly gets "stuck"
>> on some row of the table, so even when I scroll and that row is no
>> longer on top of the buffer, that row is still replaced by the header
>> line.
>
> Yes, fixed now.
Hmm, I'm experience th
Hi Jack,
Jack Kamm writes:
> Hmm, I'm experience the problem worse now -- the header is always
> getting stuck on the first row it appears on. Also, I'm seeing the
> follow error in my *Messages*:
A silly oversight on my side (I need a little break.) Fixed.
> Sure, see the patch below.
Appli
Hi Seth,
I applied your change on the maint branch:
https://code.orgmode.org/bzg/org-mode/commit/7e4e34db
Thanks!
--
Bastien
The patch below fixes a bug with the behavior of link without file for
babel source blocks. All explained in patch message, but let me know if
any concerns.
>From 25d363bbc3cd7122287364f25f9b5d653bcae232 Mon Sep 17 00:00:00 2001
From: Matt Huszagh
Date: Fri, 7 Feb 2020 23:09:48 -0800
Subject: [PA
There appears to be no way to disable the comma escape when using :wrap
for a babel source block.
I'm essentially trying to replicate this example from the manual
#+NAME: attr_wrap
#+BEGIN_SRC sh :var data="" :var width="\\textwidth" :results output
echo "#+ATTR_LATEX: :width $wi
I've added the ability in my own configuration to use lambda functions
that evaluate to a string as babel default header arguments, instead of
just the plain strings currently allowed. Would anyone else be
interested in this feature? Shall I prepare a patch?
There are a number of use cases for thi
25 matches
Mail list logo
