>> To make the handling of patches easier please use "format-patch".
>
> It looks like this was sent with git-send-email (which is fed
> format-patch output either explicitly or underneath), and it applied
> cleanly for me.
>
> My understanding is that, even though this project accepts patches as
* doc/org-manual.org (Clocking Work Time): Replace "to that you can"
with "so that you can".
---
doc/org-manual.org | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index b14c28807..b61644626 100644
--- a/doc/org-manual.org
+++
I was thinking of something like
#+ATTR_HTML: controls
#+POSTER: quadratic.png
video:quadratic.webm
exporting to the following HTML.
> That looks too rich for a link to me unless alot of it is always the
> same, or derived, e.g. the id tags.
It is quite rich. But, note that even img tags,
It would be nice to have a link type to export HTML5 videos. Currently,
the only way to insert videos is to use the #+BEGIN_video, #+END_video
block with literal #+HTML in them. This seems a little kludgy. Thoughts?
Thanks,
Arun Isaac.
signature.asc
Description: PGP signature
>> Perhaps, `org-publish-get-project-from-filename' can be rewritten
>> without `catch' and `throw' using `cl-some' or `seq-some'. This is not a
>> bug. But, it might help improve readability of the logic.
>
> Done.
Nice. Looks good.
> Note that `seq-some' is not an option since we support
Nicolas Goaziou writes:
> Hello,
>
> Arun Isaac <arunis...@systemreboot.net> writes:
>
>> On list elements of `org-publish-project-alist' with :base-extension any
>> `org-publish-get-project-from-filename' fails with error
>> (wrong-type-argument sequencep an
by concatenating several strings together. When extension `x' is
any (a symbol), this step fails.
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
code. Sorry if I am nitpicking too much.
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
> I added `org-export-global-macros' in master. It's Christmas, after all.
Thanks! And, Merry Christmas! :-)
signature.asc
Description: PGP signature
Is it possible to define macros globally, probably in the ~/.emacs init
file with some elisp, instead of on a per-file basis using the #+MACRO
keyword?
Thanks,
Arun Isaac.
signature.asc
Description: PGP signature
John Kitchin writes:
> then the preprocessing hook sounds better. You can just replace the
> links with generated html, and then export the buffer.
>
> For example, here is a function that goes through an org file and
> replaces links that are file times with image or urls, and copies the
> file
ing the HTML, and I could have used a library like xmlgen to
generate it.
Regards,
Arun Isaac
signature.asc
Description: PGP signature
> Out of curiosity, what kind of link are you using, that is dependant
> about context ?
Actually, I don't need the context of the link in the org document. I
need some properties defined in the plist of the component in
org-publish-project-alist. So, I use the info communication channel to
In the options-alist of the html backend definition,
:html-link-use-abs-url is defined twice (in lines 119 and 123). This is
possibly a typo.
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
transcoder function. Is that the recommended way to do it?
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
thought it might be a more generally useful
feature than my specific use case. So, this feature, if implemented, can
definitely wait. No hurry.
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
l feature that
the user can enable by setting some variable? Or will that be too much
trouble?
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
Footnotes in image captions are not picked up and published. Is this
intended behaviour? If it is intended behaviour, would it not be nice to
allow footnotes in image captions too?
I am using the html backend, and the following org code:
#+CAPTION: Foo [fn::bar]
[[./foo.png]]
Regards,
Arun
of the element.
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
> However, gpg signing release tag commits is dead simple and would
> take a total of maybe 10 minutes of work over the lifetime of the project
> (please correct me if I'm wrong).
I second this statement. GPG signing sounds good to me. We should do this.
> I know that https can be a bit tedious
> https://github.com/tj64/org-dp
I've seen org-dp before, but I'm confused about how it is different from
org-element functions like `org-element-interpret-data'.
Does it just add more convenience functions? If so, why not integrate
org-dp into org-mode itself? Surely, convenience functions
> I don't know if there is a "correct" way. It might depend on how
> sophisticated the document is. I usually use strings and format.
> Sometimes that is a pain though, if there is a lot of conditional
> formatting. So the question is which is easier for your situation, and I
> would say easier
> I've never played with plists before, could you please provide a code
> sample?
Do read the following section in the "GNU Emacs Lisp Reference Manual" about
property lists.
https://www.gnu.org/software/emacs/manual/html_node/elisp/Property-Lists.html
signature.asc
Description: PGP signature
Thank you,
Arun Isaac.
signature.asc
Description: PGP signature
> I'd like to try to improve on my configuration of projects but I'm
> unsure hot to use this new feature. How do you use it?
I maintain my blog with org mode. One of my preparation functions
generates an atom feed for my blog. This function uses
`org-publish-get-base-files' to get the path to
> Done in 5cd793c.
After 5cd793c, the documentation for the preparation function says
"Each preparation function is called with a single argument, the project
property". This could be clearer if it is "... the project property
list", as it is in the documentation for the completion function.
> 2. Require preparation functions to accept one parameter, the project
>plist.
I think adding project-plist as a parameter to preparation functions is
definitely more elegant.
But, I also came across this old thread where it was noted that making
project-plist a proper parameter, instead
ariable, I get a (void-variable project-plist) error.
Please find attached a minimal elisp file to reproduce the bug.
emacs -Q -l preparation-function-dynamic-scoping.el
My understanding of dynamic and lexical binding is a little foggy. So,
do let me know if I'm missing something.
Regards,
> Do you mean that you want to export inherited filetags on each headline?
> If so, it is not possible out of the box.
No, I would like to export the FILETAGS to say, below the title. I am
maintaining my blog in org mode, and I am hoping to use FILETAGS to tag
my blog posts. So, I am interested
When org-export-with-tags is set to t, tags on headlines are
exported. Is there a similar way to export FILETAGS as well?
Thanks,
Arun Isaac.
signature.asc
Description: PGP signature
> #+FILETAGS: foo
That's just what I was looking for. Thank you!
signature.asc
Description: PGP signature
tags.
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
SS. Please find attached a patch fixing this.
Regards,
Arun Isaac.
From f5e2bf625cc14efd35dcd77340b4ab380b2f3dc8 Mon Sep 17 00:00:00 2001
From: Arun Isaac <arunis...@systemreboot.net>
Date: Tue, 14 Jun 2016 01:18:55 +0530
Subject: [PATCH] ox-rss: Put email address in element
* contrib/lis
nature
>From 58c290c9308f07e44bf893331ccf9d9c5d255e04 Mon Sep 17 00:00:00 2001
From: Arun Isaac <theroarofthedra...@gmail.com>
Date: Thu, 26 May 2016 17:24:29 +0530
Subject: [PATCH] ox-rss: Encode characters to their XML entities
* contrib/lisp/ox-rss.el (org-rss-build-channel-info, o
> Please find attached the patch.
I think my patch introduces a bug in `org-rss-build-channel-info'. I'll
fix this and send a new patch soon.
signature.asc
Description: PGP signature
df Mon Sep 17 00:00:00 2001
From: Arun Isaac <theroarofthedra...@gmail.com>
Date: Wed, 25 May 2016 15:11:34 +0530
Subject: [PATCH] ox-rss: Encode characters to their XML entities
* contrib/lisp/ox-rss.el (org-rss-build-channel-info, org-rss-headline):
Encode disallowed characters in `ti
github.com/philjackson/xmlgen), or do I write my own
find and replace functions like those in ox-html? I think the xmlgen
based approach provides better abstraction and avoids reinventing XML
generation. But, it will introduce an additional dependency.
Please provide thoughts and suggestions.
Thank you,
Arun Isaac.
d patch? Thank you.
Please find attached an updated patch.
Thank you.
>From a8fd0b0f4eca51a38a432ad942b695b9e565d4fe Mon Sep 17 00:00:00 2001
From: Arun Isaac <theroarofthedra...@gmail.com>
Date: Thu, 12 May 2016 09:21:18 +0530
Subject: [PATCH] ox-rss: Prevent dropping lower level h
> This is a contributed package. I don't mind patching it but those have,
> usually, a maintainer.
Is there some other maintainer I should contact? I mean, should I be
posting bug reports and patches to contributed packages on some other
mailing list?
> Are you sure it is a bug? There's a
; = file end here =
>
> Please find attached a patch fixing this.
>
> Regards,
> Arun Isaac.
.
= file begins here =
* Headline level 1
foo
** Headline level 2
bar
= file end here =
Please find attached a patch fixing this.
Regards,
Arun Isaac.
signature.asc
Description: PGP signature
>From e000940d29b4bf5f63274e82f6a7341021000fd2 Mon Sep 17 00:00:00 2001
> the org-babel-execute:scheme function looks for a :scheme header
> argument (otherwise uses the geiser-default-implementation).
You're right. I went through ob-scheme.el. org-babel-execute:scheme does
look for a :scheme header argument.
But, my original problem was different. I was looking for
> In addition to requiring 'geiser-install you have to set the
> geiser-active-implementations variable, e.g.:
Customizing the geiser-active-implementations variable works for
me. Thank you.
> alternatively there is a :scheme header argument for src blocks:
>
> #begin_src scheme :scheme guile
very time is tedious and
annoying. Is there some way to circumvent this issue?
Thanks,
Arun Isaac.
signature.asc
Description: PGP signature
Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:
> Hello,
>
> Arun Isaac <theroarofthedra...@gmail.com> writes:
>
>> I have implemented a new option keyword, RSS_FEED_URL, for the RSS
>> exporter backend.
This is a patch I submitted some time back.
>
How long does FSF copyright assignment typically take? I sent a request
around 2 weeks ago (on December 26), but haven't received a reply yet.
Does it usually take this long? Should I resend my copyright
assignment request?
signature.asc
Description: PGP signature
> Although it is not strictly necessary for applying patches to contrib
> libraries, did you sign FSF papers already? It can matter if we consider
> moving this library into core some day.
I have initiated the process. I will get back to you once it is
complete.
signature.asc
Description: PGP
quot; ".png"
> path)))
> ;; anything else, we just do the regular thing
> (t
> (org-html-link link contents info)
>
> (org-export-define-derived-backend 'my-html 'html
> :translate-alist '((link . my-link-format)))
>
> (browse-url (org-export-to-file 'my-html "custom-link.html"))
Thank you. I'll adapt this to my needs.
Regards,
Arun Isaac
Hi,
Can we use the https link for MathJax as the default?
https://cdn.mathjax.org/mathjax/latest/MathJax.js
Currently, the default is the http link. Wouldn't having encryption by
default be nice?
Regards,
Arun Isaac
signature.asc
Description: PGP signature
the appropriate image for the
context in which it appears, and thus optimize bandwidth usage.
Thanks,
Arun Isaac.
signature.asc
Description: PGP signature
-home or
publishing-directory concatenated with the output filename of the
feed. This need not necessarily be so. So, the RSS_FEED_URL option
keyword is introduced to let the user customize the feed URL.
Please review the patch and consider for inclusion.
Thanks,
Arun Isaac.
signature.asc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Arun Isaac <theroarofthedra...@gmail.com> writes:
> Currently, the feed URL is assumed to be html-link-home or
> publishing-directory concatenated with the output filename of the
> feed. This need not necessarily be so. So, the RSS_
.
How about initializing the cache before the execution of the preparation
function? I am calling org-publish-find-title in the preparation
function, and this would address my use case. If you think this is a
good idea, I can come up with a patch.
Else, we can close this issue. It's not really a major p
zing the cache on my
own. But, I'm wondering if this can be fixed at a more fundamental
level.
Thank you,
Arun Isaac.
Emacs : GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.6)
of 2015-09-10 on foutrelis
Package: Org-mode version 8.3.1 (release_8.3.1-505-g6b2c38 @
/home/arunisa
of the error, and a
minimal init file to reproduce the bug. To reproduce the bug, just
extract the tarball, and run
emacs -Q -l minimal-org.el
Thanks,
Arun Isaac.
Emacs : GNU Emacs 24.5.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.16.6)
of 2015-09-10 on foutrelis
Package: Org-mode version 8.3.1
It works now. Thanks!
signature.asc
Description: PGP signature
Nicolas Goaziou writes:
> I made the change in master.
I think a bug has been introduced by your change.
In org-publish-projects, the variable project-plist is accessed (to get
the preparation-function) before it is bound. So, I am getting a
(void-variable
org-export-before-{processing,parsing} hooks are only useful when I have
existing source files and I want to modify them in some way before I
{process,parse} them. In my case, the source files don't exist at all,
before my preparation-function is run.
Regarding the preparation-function, the use
filenames are collected before the preparation-function
is executed, the publishing-function does not see the generated source
files.
Right now, I'm calling my preparation-function manually before calling
org-publish-project, but it would be nice if I didn't have to do it this
way.
Thanks,
Arun
Kyle Meyer writes:
> Fixed in 2c349cc65.
Everything works as expected now. Thanks a lot!
signature.asc
Description: PGP signature
60 matches
Mail list logo