Nick Dokos writes:
> That's not going to work: unquoting[fn:1] evaluates the unquoted
> element during the setting of org-capture-templates. That would have
> the effect of evaluating the function call when the setq is evaluated,
> whereas the intent here is to evaluate the
Aaron Ecay writes:
> The API has the following two functions already:
> - org-id-find-file-for: id -> file-name
> - org-id-find-id-in-file: id file -> position
>
> Imagine I add to this API org-id-find-marker: id -> marker. Then I
> think we can deprecate (and eventually
On 22 September 2016, Xi Shen wrote:
#+BEGIN_SRC sh :dir /sshx:openwrt:/mnt/sda1
ls -al
#+END_SRC
Just use ssh, not sshx, and it should work.
Bill
--
William Denton :: Toronto, Canada :: https://www.miskatonic.org/
Caveat lector.
When exporting images with captions, ox-html currently creates a strucuture
like this:
Figure 1: "test"
(I've tried setting org-html-html5-fancy" to t, but for whatever reason
this doesn't result in the useo f the tag. I tried with emacs -q
with no luck).
I would like to be able to give
On Wed, 21 Sep 2016, Philip Hudson wrote:
AFAICT :tangle takes only "yes", "no", or a literal pathname.
Stuff like
:tangle (my-lisp-function arg1 arg2)
will work.
How
might I dynamically generate a pathname for :tangle? I suppose what I
want is some kind of escape syntax for eval'ing a
Hi,
I tried this block
#+BEGIN_SRC sh :dir /sshx:openwrt:/mnt/sda1
ls -al
#+END_SRC
But I got
byte-code: Method `sshx' should specify both encoding and decoding command
or an scp program
But I could not find a way to define the encoding/decoding command...
--
Thanks,
David S.
I have a block of Perl using the GD library to generate a PNG:
#+BEGIN_SRC perl : results output :file output.png :exports results
# code to generate png
print $image -> png();
#+END_SRC
When I export, I get a buffer with the raw PNG data and the question (in the
mini-buffer):
Select
Hi Nicolas,
Thanks for your feedback. I am almost done incorporating it into the
patch. I have only two further questions.
2016ko irailak 3an, Nicolas Goaziou-ek idatzi zuen:
[...]
>> 4. A similar issue arises for org-id-find. I would like it to always
>> return a marker, rather than having
Hi,
There are various export filters, but I’d like one that just does a
complete, raw dump of the internal memory structure[*]. I could start
with something like the HTML export and work backwards to output other
tag names, but it seems like it should be possible to just dump the
data structure.
Adam Porter writes:
> li...@wilkesley.net writes:
>
>> I have a capture template which prompts for a file name and uses this
>> to create a filename with a datestamp:
>>
>> (defun capture-pelican-draft-file (path)
>> (let ((name (read-string "Name: ")))
>>
Hello,
li...@wilkesley.net writes:
> commit 5485170263a46fa17db67b0324c4c4e48bcdfe49
> Author: Nicolas Goaziou
> Date: Fri Jun 24 01:11:49 2016 +0200
>
> org-capture: Remove forbidden value type from "file" templates
>
Try wrapping `capture-pelican-draft-file' call
Hello,
Rasmus writes:
>> I think
>>
>> #+TITLEGRAPHICS: [[file:link.pdf]]
>>
>> would be cleaner.
>
> I dropped this. One might need to add attributes to the graphic. The
> #+titlegraphics approach wouldn’t allow it.
Well, wouldn't the following work?
#+attr_beamer:
"David A. Gershman" writes:
> FWIW, Eric had the solution:
>
> #+MACRO: gendate src_perl[:results output raw]{print ($1*5);}
Ah, yes, I tend to forget that :results can take multiple args.
> P.S. I should start a blog with all I learn on this. Someone could
> benefit
li...@wilkesley.net writes:
> the previous commit looks as though it
> might have been the one responsible:
>
> commit 5485170263a46fa17db67b0324c4c4e48bcdfe49
> Author: Nicolas Goaziou
> Date: Fri Jun 24 01:11:49 2016 +0200
>
> org-capture: Remove forbidden value
AFAICT :tangle takes only "yes", "no", or a literal pathname. How
might I dynamically generate a pathname for :tangle? I suppose what I
want is some kind of escape syntax for eval'ing a Lisp form, like
maybe:
:tangle %(my-dynamic-filename-generator)
Sorry if I'm missing something basic and
On Wednesday, 21 Sep 2016 at 15:22, Giacomo M wrote:
> Lately I like to have headlines for all the logical parts of the
> document, so also an "Abstract" headline with the abstract block inside.
> Then I use the tag "ignore" and the org export extra "ignore-headlines"
> (activated e.g. via
On 2016-09-21 12:54, Adam Porter wrote:
li...@wilkesley.net writes:
I have a capture template which prompts for a file name and uses this
to create a filename with a datestamp:
(defun capture-pelican-draft-file (path)
(let ((name (read-string "Name: ")))
(expand-file-name (format
Well, I ended up with my custom function then...
So case is closed.
Thank for the help anyway!
(defun me/org-map-entries (org-file in-tags func)
(let* ((tags (if (stringp in-tags)
(list in-tags)
in-tags)))
(with-temp-buffer
(org-mode)
Il 20/09/2016 17:21, Eric S Fraga ha scritto:
I had a #+include: directive as the first line of the
file which included an org file called preamble.org. In that preamble
file, the last headline had the tag :noexport:. It would seem that this
tag is not processed until after the include file
On 09/21/2016 04:49 AM, Adam Porter wrote:
> "David A. Gershman" writes:
>
>> Given the following line:
>>
>> * Date: src_perl[:results output :exports none]{print 2016;}
>>
>> The result '2016' is surrounded by '=' so that HTML export results in
>> tags surrounding
Hi Rasmus,
The patch in general LGTM. One comment/question, though:
2016ko irailak 21an, Rasmus-ek idatzi zuen:
[...]
> +(defcustom org-src-block-faces nil
> + "Alist of faces to be used for source-block.
> +Each element is a cell of the format
> +
> + (\"language\" FACE-OR-BACKGROUND)
On 09/21/2016 12:15 AM, Christian Moe wrote:
> David A. Gershman writes:
>
>
>> My org file has:
>>
>> This is line one.
>> This is line two.
>>
>> but the HTML export makes them different paragraphs...
> Does it? If they're not separated by a blank line, the exporter should run
> them
>
Perfect!! Thank you!!
I saw this option in the Manual (14.8.2.2) under /Format/, but it said
it "The results are interpreted asraw Org mode code..." so it didn't
click the results would "left alone".
Thanks again!
On 09/21/2016 12:11 AM, Eric S Fraga wrote:
> On Wednesday, 21 Sep 2016 at
"David A. Gershman" writes:
> Forgive my several questions/emails. I'm working on getting lecture
> notes ready for next week and thus am running into several questions
> with Org HTML Export. Unfortunately, my searches typically result
> in manual page hits, but my
Adam Porter writes:
> Rainer Krug writes:
>
>> But It seems to abusing the basic idea of custom-set-variables as this
>> sounds as if it is used by the customise interface.
>
> What I mean is, you can use the customize interface to store your
>
li...@wilkesley.net writes:
> I have a capture template which prompts for a file name and uses this
> to create a filename with a datestamp:
>
> (defun capture-pelican-draft-file (path)
> (let ((name (read-string "Name: ")))
> (expand-file-name (format "%s-%s.org"
>
Rainer Krug writes:
> But It seems to abusing the basic idea of custom-set-variables as this
> sounds as if it is used by the customise interface.
What I mean is, you can use the customize interface to store your
org-capture-templates. It's already set up for that. You can
"David A. Gershman" writes:
> Given the following line:
>
> * Date: src_perl[:results output :exports none]{print 2016;}
>
> The result '2016' is surrounded by '=' so that HTML export results in
> tags surrounding
> the '2016'.
>
> According to the manual section
Hi,
Thanks for the suggestions.
Sorry about the slow reply... I'm lacking time ATM.
I simplified the patch to only add the short version of properties and not
include the titlegraphics.
> I didn't test your patch. However, here are some late comments about
> this suggestion.
>
>> Maybe we can
Hi,
As discussed earlier (though I can't find the thread right now) it would
be nice to have colored source blocks not depend on new faces but on a
variable.
This patch does that.
Is that OK to push?
Thanks,
Rasmus
--
The right to be left alone is a human right
>From
Nicolas Goaziou writes:
> Hello,
>
> Now that Emacs 25.1 is out, I'd like to have Org 9.0 become the new
> stable branch.
>
> Are there outstanding bugs left out? Is there and pending patch
> important enough to block the release?
Oh my, time is flying by. I still have
On Wednesday, 21 Sep 2016 at 06:07, David A. Gershman wrote:
> Given the following line:
>
> * Date: src_perl[:results output :exports none]{print 2016;}
How about
* Date: src_perl[:results output raw]{print 2016;}
?
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.90.1, Org
I have a capture template which prompts for a file name and uses this to
create a filename with a datestamp:
(defun capture-pelican-draft-file (path)
(let ((name (read-string "Name: ")))
(expand-file-name (format "%s-%s.org"
(format-time-string "%Y-%m-%d")
On Tuesday, 20 Sep 2016 at 23:32, Charles C. Berry wrote:
> I find myself in the habit of using inlinetasks tagged noexport for
> various things and that might serve you in this case. That is, convert the
> headline section to an inlinetask.
Hi Chuck,
Yes, this would work. But, in the end,
David A. Gershman writes:
> My org file has:
>
> This is line one.
> This is line two.
>
> but the HTML export makes them different paragraphs...
Does it? If they're not separated by a blank line, the exporter should run them
together into one paragraph. Mine does.
> However, a
> On 20 Sep 2016, at 19:08, Adam Porter wrote:
>
> Rainer Krug writes:
>
>> Could you please provide an example? It is not clear to me what you mean - I
>> prefer simpler!
>
> Sure, here's an abbreviated example of custom-set-variables from my
>
Forgive my several questions/emails. I'm working on getting lecture
notes ready for next week and thus am running into several questions
with Org HTML Export. Unfortunately, my searches typically result in
manual page hits, but my problems seem to be a-typical. So...
Given the following line:
37 matches
Mail list logo