On 25/05/18 01:13, Nicolas Goaziou wrote:
Hello,
Alex Fenton writes:
As far I understand it, |:output-dir| and |:file-ext| that were
intended to be used in the global document header, applying to all
blocks.
However, it seems to mean that all blocks regardless of their :results
args then emi
> Nicolas Goaziou writes:
>
> You may
> want to tweak `org-file-apps’.
I chose `Default for unrecognized files’, `Visit with Emacs’;
but `Default for files in directory’ or use of the hidden file in the directory
for setting the mode would be better.
Thanks.
Hello,
Alex Fenton writes:
> As far I understand it, |:output-dir| and |:file-ext| that were
> intended to be used in the global document header, applying to all
> blocks.
>
> However, it seems to mean that all blocks regardless of their :results
> args then emit a file, and put their output as
Hello,
Van L writes:
> The link handling for org mode behaves unexpectedly where a file sets
> org mode according to `Local variables:' at the end of the file.
>
> In the following, a.org and b.org files work as expected using M-x
> org-store-link and M-x org-insert-link for `file:' link.
>
> Wi
Hello,
stardiviner writes:
> I set Babel default header arguments to this:
>
> ,
> | (setq-default org-babel-default-header-args
> | '((:session . "none")
> | (:noweb . "no") (:hlines . "no")
> | (:tangle . "no") (:comments . "links")
> |
Hi,
As far I understand it, |:output-dir| and |:file-ext| that were intended
to be used in the global document header, applying to all blocks.
However, it seems to mean that all blocks regardless of their :results
args then emit a file, and put their output as a [file:] link. It's not
clear
Hello Nicolas,
I'm sorry for the delay, this problem drove me crazy for a few days.
So I started again from the beginning and, of course, I am now unable to
replicate my original test case.
So, I think you could delete the
0001-Manage-the-encoding-of-files-with-include-.patch patch.
I am really so
Hi Aaron,
I just went ahead and removed that "---" syntax from ox-hugo. Updated links:
1. https://ox-hugo.scripter.co/doc/details-and-summary/
2. https://ox-hugo.scripter.co/test/posts/details-and-summary/
(it was easy as I had committed that feature just yesterday.)
On Thu, May 24, 2018 at 3:0
Hello,
aldo ridhoni writes:
> https://orgmode.org/manual/Emphasis-and-monospace.html#Emphasis-and-monospace
>
> https://orgmode.org/guide/Emphasis-and-monospace.html#Emphasis-and-monospace
>
> The manual and guide is different in code and verbatim text. Which one is
> the right one?
The manual
Hi Kaushal,
2018ko maiatzak 24an, Kaushal Modi-ek idatzi zuen:
>
> Yes, the proposal though supports these 2 things specific to details
> element:
>
> 1. Detecting "open" attribute via "#+attr_html: open".
Is it important for open to be a “bare” attribute (not sure of the
official name) like “”
Hi Aaron,
On Thu, May 24, 2018 at 2:36 PM Aaron Ecay wrote:
>
> I wasnʼt thinking about multiparagraph summaries. But actually, I
> realize that your suggestion in response would work with only one small
> change to a variable in ox-html.
Yes, the proposal though supports these 2 things speci
Hi Kaushal,
2018ko maiatzak 24an, Kaushal Modi-ek idatzi zuen:
>
> HTML allows multi-paragraph summaries.. (see my test link above). Expanding
> on your idea.. what if we had another Special block with name summary?
I wasnʼt thinking about multiparagraph summaries. But actually, I
realize that
Hello Aaron,
On Thu, May 24, 2018 at 2:08 PM Kaushal Modi wrote:
> Expanding on your idea.. what if we had another Special block with name
> summary?
>
> #+begin_details
> #+begin_summary
> Open for details
>
> More summary.
> #+end_summary
> Many details here.
> #+end_details
>
>From quick tes
Hi Aaron,
Thanks for the feedback.
On Thu, May 24, 2018 at 1:42 PM Aaron Ecay wrote:
> Hi Kaushal,
>
> It seems like a good idea. My two comments are:
>
> - Remember that ox-html can export to HTML4, so the code would need to
> detect that case and have a sensible fallback
>
Yes, I think th
Hi Kaushal,
It seems like a good idea. My two comments are:
- Remember that ox-html can export to HTML4, so the code would need to
detect that case and have a sensible fallback
- The approach of looking for “magic” strings in the contents seems
hackish. What if the summary was treated as a
Hello,
Yesterday, I came up with a way to generate the HTML details disclosure
fairly easily using Org Special Blocks. I implemented that in ox-hugo. But
I believe the same would be useful for ox-html too.
Here's the relevant code snippet:
((string= block-type "details")
;; Recognize O
Hi
Thierry Banel one of the authors of orgtbl-aggregate.el
Suggested to me the following code, if just want to extract one column
of a table.
#+TBLNAME: raw-data
| 1 | a | 3 |
| 2 | b | 4 |
| 3 | c | 6 |
| 4 | d | 7 |
#+BEGIN_SRC elisp :var data=raw-data
(mapcar (lambda (line)
(li
aldo ridhoni writes on Tue 1 May 2018 02:28:
> https://orgmode.org/manual/Emphasis-and-monospace.html#Emphasis-and-monospace
>
> https://orgmode.org/guide/Emphasis-and-monospace.html#Emphasis-and-monospace
>
> The manual and guide is different in code and verbatim text. Which one is
> the
18 matches
Mail list logo
