Re: [O] "#+BEGIN_SRC mail" and org-src-fontify-natively
Hello, Andrea Rossetti writes: > Hello Org users, > > when I start emacs -Q and do the following recipe: > > 1) open the test file "prova.org" (see attach) > 2) confirm at the file-local variable prompt, by typing "y" > 3) quit with C-x C-c > > then Emacs unexpectedly asks for a confirm to save the > modified buffer "org-src-fontify:mail-mode", even if I took care > to avoid any editing between steps 2) and 3). > > The unexpected confirm is not asked if the same recipe is replayed > with a modified "prova.org", where org-src-fontify-natively has been > set to nil instead of t. > > May I please ask: it's reproducible for you as well? any clue on > how to suppress that annoying confirm? Thanks in advance for your > suggestions. I cannot reproduce it on development branch. It may have been fixed. > Another minor issue is that "To:" and "Subject:" aren't fontified > if the mail text is indented by two spaces (typically added by default > if you edit the block by typing C-c '). Not a big deal, just to let > you know. One could just avoid using C-c ' and align the mail text > at left side. The issue is visible in the buffer window, but > HTML export is not affected, it works fine. You may want to set `org-edit-src-content-indentation' to 0. Regards, -- Nicolas Goaziou
[O] shrink latex table to fit beamer slide
Dear Org experts,
I am trying to fit a slightly wide latex table into a beamer
slide in org. Below is my current solution and I was wondering
if anyone can offer some advice on improving it.
#+begin_scriptsize
#+ATTR_LATEX: :align p{1cm} p{0.5cm} p{1cm}
| | | <7> |
| Site | Ind | -log10.pval |
| 123279713 | 1 | 6.006102 |
| 123279713 | 2 | 6.274326 |
| 123279713 | 4 | 6.210920 |
| 123279710 | 4 | 97.163695 |
| 123279710 | 5 | 208.841892 |
#+end_scriptsize
In this solution, the issues are: (1) for column width
doesn’t seem to round text for latex output, and (2) I need
to define column width in addition to .
I’d like to seek a solution that just shrinks the table to fit
the text width without this fiddling.
Many thanks,
Zhihao
[O] demoting a heading inserts spaces in column-0 text
There was a change (cba2f0a2a3024ae5bf71e1a12ba99778a92902a2, Sat Nov 8 14:35:24 2014 +0100) which made :CLOCK: etc entries shift to the right when the tree is being shifted to the right („demoted“, e.g. using M-S-Right). But now it changes from this: some :CLOCK: CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 :END: Text to this: * some :CLOCK: CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 :END: Text while what I expected was this: * some :CLOCK: CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 :END: Text Proposal: if text starts in column 0, don't move the text; move only the headers. An old behaviour (reported in http://permalink.gmane.org/gmane.emacs.orgmode/92450) was not to move anything in this case, that's bad and was fixed. I think the proposal is better. org-adapt-indentation=nil would write all headers in column 0 by default, which is ugly and doesn't give the desired result. If some people prefer „move header+text even if text is in column 0“ (current behaviour) over „move header but not text if text is in column 0“ (proposal), org-adapt-indentation could select choose between the two. Thanks, Daniel
Re: [O] shrink latex table to fit beamer slide
Hi Zhihao,
Zhihao Ding writes:
> Dear Org experts,
>
> I am trying to fit a slightly wide latex table into a beamer
> slide in org. Below is my current solution and I was wondering
> if anyone can offer some advice on improving it.
>
> #+begin_scriptsize
> #+ATTR_LATEX: :align p{1cm} p{0.5cm} p{1cm}
> | | | <7> |
> | Site | Ind | -log10.pval |
> | 123279713 | 1 | 6.006102 |
> | 123279713 | 2 | 6.274326 |
> | 123279713 | 4 | 6.210920 |
> | 123279710 | 4 | 97.163695 |
> | 123279710 | 5 | 208.841892 |
> #+end_scriptsize
>
> In this solution, the issues are: (1) for column width
> doesn’t seem to round text for latex output, and (2) I need
> to define column width in addition to .
> I’d like to seek a solution that just shrinks the table to fit
> the text width without this fiddling.
>
> Many thanks,
> Zhihao
>
first:
you can set the font size in the #+ATTR_LATEX: line with
#+ATTR_LATEX: :font \scriptsize
second:
If you want to get the numbers rounded, you can either
(a) use babel or
(b) use the spreadsheet capabilities.
In both cases, you'll generate a new table which you want to export
example:
--8<---cut here---start->8---
* orig table :noexport:
#+name: origtable
| | | <7> |
| Site | Ind | -log10.pval |
| 123279713 | 1 | 6.006102 |
| 123279713 | 2 | 6.274326 |
| 123279713 | 4 | 6.210920 |
| 123279710 | 4 | 97.163695 |
| 123279710 | 5 | 208.841892 |
* the table formatted with babel
This (untested!) used to work, but due to a bug [fn:1] does not.
#+name: formatorigtable
#+begin_src R :var origtable=origtable :colnames yes
origtable[,3] <- format(origtable[,3], digits=3)
origtable
#+end_src
#+ATTR_LATEX: :align p{1cm} p{0.5cm} p{1cm}
#+results: formatorigtable
* the table formatted with calc/orgmode
This is quite complicated but works.
| | | <7> |
| Site | Ind | -log10.pval |
|---+-+-|
| 123279713 | 1 |6.01 |
| 123279713 | 2 |6.27 |
| 123279713 | 4 |6.21 |
| 123279710 | 4 | 97.16 |
| 123279710 | 5 | 208.84 |
#+TBLFM: $1=remote(origtable, @@#$1)::$2=remote(origtable,
@@#$2)::$3=remote(origtable, @@#$3); f-2
* Footnotes
[fn:1] I am unable to locate the thread about this for some strange reason.
The messages were sent between 2014-10-14 and 2014-10-16.
--8<---cut here---end--->8---
Best,
Andreas
[O] BUG: table variable passing broken
Hi, This issue is still open. And I do not seem to be able to find this thread on gmane for some reason. So, I resend the last message as a summary. EDIT: I just tried to answer to that thread but the message again did not come through. So, another try (with a slightly adapted title). Best, Andreas Andreas Leha writes: >> Charles Berry writes: >>> Andreas Leha med.uni-goettingen.de> writes: >>> =20 Hi all, =20 There seems to be a bug in table passing as variables now using the tangle-friendly version of passing variables. =20 Here is an example (I get an error also with emacs -Q): =20 --8<---cut here---start->8--- * test #+name: testtab | variable | display | unit | |---+---+---| | num_cells | Number of Cells in Well | | | cell_area | Cell Area | =CE=BCm=C2=B2= > | | nucleus_area | Nucleus Area | =CE=BCm=C2=B2= > | | roundness | Cell Roundness| | | ratio_w2l | Cell Width to Length Ratio| | | inten_nuc_dapi_median | Intensity Nucleus DAPI Median | | | dapi_median | Intensity Nucleus DAPI Median | | | edu_median| Intensity edu Median | | | oct4_median | Intensity oct4 Median | | | clump_size| Clump Size| cells | | short_name| Cell Line | | | p_col | Column| | | batch | Batch | | | concentration | Fibronectin Concentration | ugml | | Residual | Residual | | | evaluation_guid | Plate | | | donor | Genotype | | =20 #+BEGIN_SRC R :session *test* :var test=3Dtesttab test #+END_SRC =20 #+RESULTS: --8<---cut here---end--->8--- =20 I see this in my R session: =20 --8<---cut here---start->8--- Error in scan(file, what, nmax, sep, dec, quote, skip, nlines,=20 na.strings, (from testorg.org!917613Wp#22) :=20 line 17 did not have 3 elements --8<---cut here---end--->8--- =20 >>> >>> I think this is the wrong diagnosis. >> >> I agree. Saving the table as tsv (via org-table-export) results >> in a file that cannot be read from R either. >> >>> >>> Did you actually revert to the earlier version of ob-R.el to confirm tha= >t=20 >>> this would have run correctly?=20 >> >> I did not revert. But that org file used to work. I won't be able >> to bisect any time soon. >> >>> >>> The reason I ask is that I just tried this with org-babel-R-assign-elisp >>> from=20 >>> >>> org-mode-a5686d87786b1d6514ec85959a2188f703346a06/lisp/ob-R.el >>> >>> and got the same error. Note this: >>> >>> >>> #+name: testtab2 >>> | variable | display | unit | >>> |--+--+--| >>> | donor| Genotype | | >>> >>>=20=20=20 >>> #+BEGIN_SRC emacs-lisp :var test=3Dtesttab2 >>> (orgtbl-to-tsv test '(:fmt org-babel-R-quote-tsv-field)) >>> #+END_SRC >>> >>> #+RESULTS: >>> : "donor" "Genotype" >>> >> >> exactly. That also causes the org-table-export to fail. >> >>> >>> #+BEGIN_SRC emacs-lisp :var value=3Dtesttab2 >>> ;; from org-babel-R-assign-elisp >>> (mapcar 'length (org-remove-if-not 'sequencep value)) >>> #+END_SRC >>> >>> #+RESULTS: >>> | 3 | >>> >>> In particular, the empty table cells are omitted even though=20 >>> >>> `value' or `test' has all lengths as 3. This results in=20 >>> calling read.table ( ..., fill=3DFALSE) implicitly. >>> >>> Not sure if the fix is to retool org-babel-R-assign-elisp or something >>> in org-table.el. >>> >> >> I am the wrong person to answer that. But it looks to me to be an >> issue for org-table.el. >> >> Thanks for your better analysis. >> >> Regards, >> Andreas > >To keep this issue going, here a quick thought: > >Since orgtbl-to-csv seems to work, a temporary fix on ob-R's side would >be to use that for passing of tables. > >Andreas >
Re: [O] [RFC] Change property drawer syntax
Hi Nicolas, It looks the commit 8d8ad983823c63b13fd6b471ce9db8c2f95e3808 broke generation of org sparse trees, when searching with properties that are not all uppercase. The fix seems to be just removing the conversion of key to upcase in `org-entry-properties'. Since the comparison with special properties is being done by a case insensitive check, this should be the only fix required? There are no test failures, and the conversion to uppercase seems to have been introduced only in this change, so it should be OK? diff --git a/lisp/org.el b/lisp/org.el index e806440..8cbbcc4 100755 --- a/lisp/org.el +++ b/lisp/org.el @@ -15703,7 +15703,7 @@ strings." ;; after its extension. We also forbid standard ;; properties to be named as special properties. (while (re-search-forward org-property-re end t) - (let* ((key (upcase (org-match-string-no-properties 2))) + (let* ((key (org-match-string-no-properties 2)) (extendp (org-string-match-p "\\+\\'" key)) (key-base (if extendp (substring key 0 -1) key)) (value (org-match-string-no-properties 3))) Thanks, Puneeth
Re: [O] shrink latex table to fit beamer slide
Thanks a lot Andreas. Is there a way to globally
shrink/resize table for latex export without having
to define column width like this
“:align p{1cm} p{0.5cm} p{1cm}” ?
I am hopting to do something like width=\textwidth
and leave the rest to org for finding suitable font
sizes.
Zhihao
> On 5 Dec 2014, at 13:12, Andreas Leha
> wrote:
>
> Hi Zhihao,
>
>
>
> Zhihao Ding writes:
>> Dear Org experts,
>>
>> I am trying to fit a slightly wide latex table into a beamer
>> slide in org. Below is my current solution and I was wondering
>> if anyone can offer some advice on improving it.
>>
>> #+begin_scriptsize
>> #+ATTR_LATEX: :align p{1cm} p{0.5cm} p{1cm}
>> | | | <7> |
>> | Site | Ind | -log10.pval |
>> | 123279713 | 1 | 6.006102 |
>> | 123279713 | 2 | 6.274326 |
>> | 123279713 | 4 | 6.210920 |
>> | 123279710 | 4 | 97.163695 |
>> | 123279710 | 5 | 208.841892 |
>> #+end_scriptsize
>>
>> In this solution, the issues are: (1) for column width
>> doesn’t seem to round text for latex output, and (2) I need
>> to define column width in addition to .
>> I’d like to seek a solution that just shrinks the table to fit
>> the text width without this fiddling.
>>
>> Many thanks,
>> Zhihao
>>
>
> first:
> you can set the font size in the #+ATTR_LATEX: line with
> #+ATTR_LATEX: :font \scriptsize
>
> second:
> If you want to get the numbers rounded, you can either
> (a) use babel or
> (b) use the spreadsheet capabilities.
> In both cases, you'll generate a new table which you want to export
>
> example:
>
> --8<---cut here---start->8---
> * orig table :noexport:
> #+name: origtable
> | | | <7> |
> | Site | Ind | -log10.pval |
> | 123279713 | 1 | 6.006102 |
> | 123279713 | 2 | 6.274326 |
> | 123279713 | 4 | 6.210920 |
> | 123279710 | 4 | 97.163695 |
> | 123279710 | 5 | 208.841892 |
>
>
> * the table formatted with babel
> This (untested!) used to work, but due to a bug [fn:1] does not.
>
> #+name: formatorigtable
> #+begin_src R :var origtable=origtable :colnames yes
> origtable[,3] <- format(origtable[,3], digits=3)
>
> origtable
> #+end_src
>
> #+ATTR_LATEX: :align p{1cm} p{0.5cm} p{1cm}
> #+results: formatorigtable
>
>
> * the table formatted with calc/orgmode
> This is quite complicated but works.
>
> | | | <7> |
> | Site | Ind | -log10.pval |
> |---+-+-|
> | 123279713 | 1 |6.01 |
> | 123279713 | 2 |6.27 |
> | 123279713 | 4 |6.21 |
> | 123279710 | 4 | 97.16 |
> | 123279710 | 5 | 208.84 |
> #+TBLFM: $1=remote(origtable, @@#$1)::$2=remote(origtable,
> @@#$2)::$3=remote(origtable, @@#$3); f-2
>
> * Footnotes
>
> [fn:1] I am unable to locate the thread about this for some strange reason.
> The messages were sent between 2014-10-14 and 2014-10-16.
> --8<---cut here---end--->8---
>
> Best,
> Andreas
>
>
Re: [O] shrink latex table to fit beamer slide
Hi Zhihao,
Zhihao Ding writes:
> Thanks a lot Andreas. Is there a way to globally
> shrink/resize table for latex export without having
> to define column width like this
> “:align p{1cm} p{0.5cm} p{1cm}” ?
> I am hopting to do something like width=\textwidth
> and leave the rest to org for finding suitable font
> sizes.
>
For that I'd let LaTeX do the job and use
\resizebox{\textwidth}{!}{}
as in
#+LaTeX: \resizebox{\textwidth}{!}{
| | | <7> |
| Site | Ind | -log10.pval |
| 123279713 | 1 | 6.006102 |
| 123279713 | 2 | 6.274326 |
| 123279713 | 4 | 6.210920 |
| 123279710 | 4 | 97.163695 |
| 123279710 | 5 | 208.841892 |
#+LaTeX: }
Best,
Andreas
> Zhihao
>
>
>> On 5 Dec 2014, at 13:12, Andreas Leha
>> wrote:
>>
>> Hi Zhihao,
>>
>>
>>
>> Zhihao Ding writes:
>>> Dear Org experts,
>>>
>>> I am trying to fit a slightly wide latex table into a beamer
>>> slide in org. Below is my current solution and I was wondering
>>> if anyone can offer some advice on improving it.
>>>
>>> #+begin_scriptsize
>>> #+ATTR_LATEX: :align p{1cm} p{0.5cm} p{1cm}
>>> | | | <7> |
>>> | Site | Ind | -log10.pval |
>>> | 123279713 | 1 | 6.006102 |
>>> | 123279713 | 2 | 6.274326 |
>>> | 123279713 | 4 | 6.210920 |
>>> | 123279710 | 4 | 97.163695 |
>>> | 123279710 | 5 | 208.841892 |
>>> #+end_scriptsize
>>>
>>> In this solution, the issues are: (1) for column width
>>> doesn’t seem to round text for latex output, and (2) I need
>>> to define column width in addition to .
>>> I’d like to seek a solution that just shrinks the table to fit
>>> the text width without this fiddling.
>>>
>>> Many thanks,
>>> Zhihao
>>>
>>
>> first:
>> you can set the font size in the #+ATTR_LATEX: line with
>> #+ATTR_LATEX: :font \scriptsize
>>
>> second:
>> If you want to get the numbers rounded, you can either
>> (a) use babel or
>> (b) use the spreadsheet capabilities.
>> In both cases, you'll generate a new table which you want to export
>>
>> example:
>>
>> --8<---cut here---start->8---
>> * orig table:noexport:
>> #+name: origtable
>> | | | <7> |
>> | Site | Ind | -log10.pval |
>> | 123279713 | 1 | 6.006102 |
>> | 123279713 | 2 | 6.274326 |
>> | 123279713 | 4 | 6.210920 |
>> | 123279710 | 4 | 97.163695 |
>> | 123279710 | 5 | 208.841892 |
>>
>>
>> * the table formatted with babel
>> This (untested!) used to work, but due to a bug [fn:1] does not.
>>
>> #+name: formatorigtable
>> #+begin_src R :var origtable=origtable :colnames yes
>> origtable[,3] <- format(origtable[,3], digits=3)
>>
>> origtable
>> #+end_src
>>
>> #+ATTR_LATEX: :align p{1cm} p{0.5cm} p{1cm}
>> #+results: formatorigtable
>>
>>
>> * the table formatted with calc/orgmode
>> This is quite complicated but works.
>>
>> | | | <7> |
>> | Site | Ind | -log10.pval |
>> |---+-+-|
>> | 123279713 | 1 |6.01 |
>> | 123279713 | 2 |6.27 |
>> | 123279713 | 4 |6.21 |
>> | 123279710 | 4 | 97.16 |
>> | 123279710 | 5 | 208.84 |
>> #+TBLFM: $1=remote(origtable, @@#$1)::$2=remote(origtable,
>> @@#$2)::$3=remote(origtable, @@#$3); f-2
>>
>> * Footnotes
>>
>> [fn:1] I am unable to locate the thread about this for some strange reason.
>> The messages were sent between 2014-10-14 and 2014-10-16.
>> --8<---cut here---end--->8---
>>
>> Best,
>> Andreas
>>
>>
[O] (org-agenda-to-appt) with sexp org-diary-class entry?
None of my events which are scheduled with org-diary-class sexp entries seem to get pushed with (org-agenda-to-appt) (for triggering alarms etc.). Is this simply a limitation of sexp org-diary-class? Is there are workaround, or would it be better to simply schedule such events as (infinitely) repeating?
[O] :colnames behavior
In this example, setting :colnames to no produces column names in the evaluated result - setting it to yes (or defaulting to nil) takes out the column names. That seems to be the opposite of what is intended - it also contradicts the manual[fn:1] afaict. --8<---cut here---start->8--- #+name: foo | a | b | |---+---| | 1 | 1 | | 2 | 2 | | 3 | 3 | #+BEGIN_SRC elisp :var tbl=foo :results drawer :colnames no (orgtbl-to-tsv tbl nil) #+END_SRC #+RESULTS: :RESULTS: a b 1 1 2 2 3 3 :END: --8<---cut here---end--->8--- Org-mode version 8.3beta (release_8.3beta-613-g40a5b7) Footnotes: [fn:1] (info "(org) colnames") -- Nick
Re: [O] (org-agenda-to-appt) with sexp org-diary-class entry?
Hi Benjamin, > None of my events which are scheduled with org-diary-class sexp entries > seem to get pushed with (org-agenda-to-appt) (for triggering alarms > etc.). Is this simply a limitation of sexp org-diary-class? Is there > are workaround, or would it be better to simply schedule such events as > (infinitely) repeating? out of curiosity I tried out that org-diary-class thing. (Org-mode version 8.3beta) The doc says about org-diary-class: #v+ This function is obsolete since ; use `org-class' instead. #v- So I used org-class. I don't know if this really matters. If not then please just take it as a side note. With the subtree #v+ * org-class appointment <%%(org-class 2014 12 1 2014 12 23 5 )> #v- in one of my agenda-files I get the respective line #v+ appts: org-class appointment #v- in the agenda. Does this help? Best regards, Marco -- http://www.wahlzone.de GPG: 0x49010A040A3AE6F2
[O] org-id-open misses invisible entries
Hello, I apologize if this remark is useless or inappropriate, I am quite new to emacs and org-mode. I noticed that the function org-id-open in org-id.el does not jump to the target entry if it is invisible. I tested that inserting (widen) before (goto-char m) in the function's defun fixes this issue. Best regards, Eric Danan
Re: [O] clock gone error, fixing it issues, and K does not clock out
i got it to occur by sorting a different tree later in the file. it occurs even after undo. On 11/18/14, Samuel Wales wrote: > maint. > > when i am clocking something, when i clock out, it says byte-code: > Clock start time is gone. > > the only way i have found to deal with it is to cancel. messages says: > Clock gone, cancel the timer anyway. > Clock canceled > No active clock. > > then i have to start the clock again. it offers me a lot of options. > i choose K. > > but contrary to the docstring, the clock is still running. so i have > to clock out. > > but that leaves a zero-length clock entry, so i have to kill it. > > maybe this is pebcak, but if so, i don't know where within that conduit. > > i'm kind of amazed that heavy clockers haven't been all over these > issues on the list before. is it just me? > > thanks. > > samuel > > -- > The Kafka Pandemic: http://thekafkapandemic.blogspot.com > > The disease DOES progress. MANY people have died from it. And > ANYBODY can get it. > > Denmark: free Karina Hansen NOW. > -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. And ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] [RFC] Change property drawer syntax
Hello, Puneeth Chaganti writes: > It looks the commit 8d8ad983823c63b13fd6b471ce9db8c2f95e3808 broke > generation of org sparse trees, when searching with properties that > are not all uppercase. Could you provide an ECM? > The fix seems to be just removing the conversion of key to upcase in > `org-entry-properties'. Since the comparison with special properties > is being done by a case insensitive check, this should be the only fix > required? There is another check, case-sensitive this time, for duplicate properties just below. Anyway, I think the problem lies in the fact that, somewhere in the internals of the function generating the spare tree, there is a case-sensitive search. Regards, -- Nicolas Goaziou
Re: [O] demoting a heading inserts spaces in column-0 text
Hello, Daniel Clemente writes: > There was a change (cba2f0a2a3024ae5bf71e1a12ba99778a92902a2, Sat > Nov 8 14:35:24 2014 +0100) which made :CLOCK: etc entries shift to > the right when the tree is being shifted to the right („demoted“, > e.g. using M-S-Right). > > > But now it changes from this: > > some > :CLOCK: > CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 > :END: > Text > > > > to this: > > * some >:CLOCK: >CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 >:END: > Text > > > >while what I expected was this: > > * some >:CLOCK: >CLOCK: [2013-11-12 Sel 10:45]--[2013-11-12 Sel 11:40] => 0:55 >:END: > Text > > > > >Proposal: if text starts in column 0, don't move the text; move >only the headers. Then, in this case, :CLOCK: drawer will not move either. Unless "headers" is defined as "stuff not too far from the headline". But it is too vague to be usable. >An old behaviour (reported in > http://permalink.gmane.org/gmane.emacs.orgmode/92450) was not to move > anything in this case, that's bad and was fixed. I think the proposal is > better. >org-adapt-indentation=nil would write all headers in column 0 by >default, which is ugly and doesn't give the desired result. There no such thing as a your "headers" in Org. :CLOCK: and "Text" are treated equally, as contents of the headline. Regards, -- Nicolas Goaziou
Re: [O] Bug: header-args:C++ doesn't work
Hello, Puneeth Chaganti writes: > I was helping out "ablephar`" on IRC and they found that setting a > file property `header-args:C++` does not work. > > After some edebug magic, I discovered that org has a feature that lets > you append property values! (Not the best way to discover a great > feature, I must say! :-) > > The fix could either be a documentation fix. (I would've tried using > cpp instead of C++, if I knew that was supported). But, this would > still have some users seeing things broken and then looking up docs or > trying out the alternative. > > OR > > a "hacky" fix, (better for the users ?), could be to consider KEY+ to > be indicating appending, but KEY++ to not. Thoughts? I prefer the former. Forbidding to end properties with "+" (unless we are appending a value) is, IMO, a bearable restriction. Regards, -- Nicolas Goaziou
Re: [O] [PATH] Speedups to org-table-recalculate
Nathaniel Flath writes: > Sorry, that was incorrect - real patches attached. Thanks. > +(defun org-table-message-once-per-second (t1 &rest args) > + "If there has been more than one second since T1, display message. > +ARGS are passed as arguments to the 'message' function. Returns > +current time if a message is printed, otherwise returns t1.. If > +T1 is nil, always messages." > + (let ((curtime (current-time))) > +(when (or (not t1) (< 0 (nth 1 (time-subtract curtime t1 > + (apply message args) > + curtime)) > +t1) The docstring seems incorrect, as the function always returns T1, no matter if a message is printed or not. > + (setq log-last-time > + (org-table-message-once-per-second > +(when all log-last-time) Nitpick: (and all log-last-time) > + (when all log-last-time) Ditto. > + (when all log-first-time) Ditto. Regards,
[O] How to export strings froom options to JS variables?
Hi all, I have this near the beginning my Org file: #+ATTR_COOL: How cool is that! I want it to be exported to something like var how_cool = 'How cool is that!' There is a problem, hovever, what happens if some clever kid exploited it, putting things like apostrophes into the string: #+ATTR_COOL: It's nice! which gets exported to