[O] [PATCH] ox-rss: Fix typos
--- contrib/lisp/ox-rss.el | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/contrib/lisp/ox-rss.el b/contrib/lisp/ox-rss.el index 10f2cc244..bb069dadf 100644 --- a/contrib/lisp/ox-rss.el +++ b/contrib/lisp/ox-rss.el @@ -22,8 +22,8 @@ ;;; Commentary: -;; This library implements a RSS 2.0 back-end for Org exporter, based on -;; the `html' back-end. +;; This library implements an RSS 2.0 back-end for Org exporter, based +;; on the `html' back-end. ;; ;; It requires Emacs 24.1 at least. ;; @@ -85,7 +85,7 @@ :package-version '(Org . "8.0")) (defcustom org-rss-image-url "https://orgmode.org/img/org-mode-unicorn-logo.png; - "The URL of the an image for the RSS feed." + "The URL of the image for the RSS feed." :group 'org-export-rss :type 'string) @@ -143,7 +143,7 @@ When nil, Org will create ids using `org-icalendar-create-uid'." ;;;###autoload (defun org-rss-export-as-rss ( async subtreep visible-only) - "Export current buffer to a RSS buffer. + "Export current buffer to an RSS buffer. If narrowing is active in the current buffer, only export its narrowed part. @@ -173,7 +173,7 @@ non-nil." ;;;###autoload (defun org-rss-export-to-rss ( async subtreep visible-only) - "Export current buffer to a RSS file. + "Export current buffer to an RSS file. If narrowing is active in the current buffer, only export its narrowed part. -- 2.20.1
Re: [O] Exporting in html with numeric references to headlines
Shérab writes: > Dear all, > > Assume the following document: > > === > > #+title: test1 > > * Introduction > > Monads will be explained in chapter [[#monads]] > > * Monads > :PROPERTIES: > :CUSTOM_ID: monads > :END: > > Welcome to the monads chapter. > > === > > When I export this to html, the paragraph in the introduction says: > > Monads will be explained in chapter 2 > > with "2" being a link, which is what I am expecting. However the link > does not work and it seems the "#monads" anchor is actually not created. > I can also observe that the links in the table of contents do not seem > to work either. > Am I doing something wrong? I also tried different variations with > <> but was not able to make anything work. As Bruno Barbier points out, you are probably OK: you just have to add more stuff in the first chapter, so that when you click the link, the change is visible. Another way to see it is to look at the HTML file that is produced: if that contains what you expect, then you should be OK. That is a technique that is often useful in debugging export problems, e.g. I often export to PDF (via LaTeX) and I look at the produced LaTeX file (and sometimes tinker with it and process it until I figure out what's wrong). In this case, the HTML looks like this: , | ... | | 1 Introduction | | | Monads will be explained in chapter 2 | | | | | 2 Monads | | | Welcome to the monads chapter. | | | | ... ` which looks correct: the #monads href links the tag. To test Bruno's hypothesis, I even added a bunch of , | Lorem ipsum ` lines between the chapters right in the HTML file to make the second chapter move down "below the fold" and see whether clicking the link works: it did. HTH. -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
Re: [O] Exporting in html with numeric references to headlines
Hi Shérab, Shérab writes: > Dear all, > > Assume the following document: > > === > > #+title: test1 > > * Introduction > > Monads will be explained in chapter [[#monads]] > > * Monads > :PROPERTIES: > :CUSTOM_ID: monads > :END: > > Welcome to the monads chapter. > > === > > When I export this to html, the paragraph in the introduction says: > > Monads will be explained in chapter 2 > > with "2" being a link, which is what I am expecting. However the link > does not work and it seems the "#monads" anchor is actually not created. > I can also observe that the links in the table of contents do not seem > to work either. > Am I doing something wrong? I also tried different variations with > <> but was not able to make anything work. > > Many thanks in advance for any hint! > FWIW, I can not reproduce (org 9.2.3). All links are created and are working; your document looks correct to me. Did you try with a longer document ? (your example is so small that there is no display difference when clicking any links). Bruno > Shérab.
[O] Exporting in html with numeric references to headlines
Dear all, Assume the following document: === #+title: test1 * Introduction Monads will be explained in chapter [[#monads]] * Monads :PROPERTIES: :CUSTOM_ID: monads :END: Welcome to the monads chapter. === When I export this to html, the paragraph in the introduction says: Monads will be explained in chapter 2 with "2" being a link, which is what I am expecting. However the link does not work and it seems the "#monads" anchor is actually not created. I can also observe that the links in the table of contents do not seem to work either. Am I doing something wrong? I also tried different variations with <> but was not able to make anything work. Many thanks in advance for any hint! Shérab.
Re: [O] Cross reference in TeXinfo export
Hello,
Carsten Dominik writes:
> I noticed that the link in the following line in org-guide.org
>
> This document is a much compressed derivative of the
> [[info:org][comprehensive Org mode manual]].
>
>
> gets turned into this in orgguide.texi
>
> @ref{Top,comprehensive Org mode manual,,org,}.
>
>
> The PDF version of the guide then looks like this:
>
> This document is a much compressed derivative of the org.
>
>
> So the link description in the PDF version is just "org", the name of the
> info node. I think the link text should be "comprehensive Org mode
> manual". Is anyone familiar enough with the texinfo exporter and texinfo
> to fix this?
Actually, this is not about the Texinfo exporter (ox-texinfo.el), but
the library responsible for handling info links (ol-info.el).
Maybe we should use
@ref{Top,comprehensive Org mode manual,,org,comprehensive Org mode manual}
instead. But what should we do when a section is specified, e.g.,
@ref{Section Name, description,,org,}
?
Regards,
--
Nicolas Goaziou
Re: [O] patch: adding split-window-right option for src block editing
Hello, "Fraga, Eric" writes: > most of my work now involves using quite large wide monitors and having > the editing of src blocks open windows below is less convenient than > splitting horizontally. I have added the option to split > horizontally. See attached patch. Thank you. Could you provide an entry in ORG-NEWS, too? > > However, ideally, I would like the option to specify a function as > context matters: sometimes a vertical split is better, sometimes > not. But implementing this was beyond my emacs-fu. Allowing one to use a function is easy. It entails one additional value in the defcustom, and one case in `org-src-switch-to-buffer': ((pred functionp) (funcall org-src-window-setup)) probably near the end since some symbols also are function names (e.g., `other-frame'). Implementing an interesting function is harder, but not necessary for Org for the time being. Regards, -- Nicolas Goaziou
Re: [O] Feature request: add leading zeroes to align ordered lists with indexes of different length
I don't think it would be as visually pleasant, but I would be grateful for it. On Sat, Jul 13, 2019 at 5:09 PM Samuel Wales wrote: > would spaces work for you too? > > -- > The Kafka Pandemic > > What is misopathy? > > https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html > > The disease DOES progress. MANY people have died from it. And ANYBODY > can get it at any time. >
[O] Cross reference in TeXinfo export
Hi,
I noticed that the link in the following line in org-guide.org
This document is a much compressed derivative of the
[[info:org][comprehensive Org mode manual]].
gets turned into this in orgguide.texi
@ref{Top,comprehensive Org mode manual,,org,}.
The PDF version of the guide then looks like this:
This document is a much compressed derivative of the org.
So the link description in the PDF version is just "org", the name of the
info node. I think the link text should be "comprehensive Org mode
manual". Is anyone familiar enough with the texinfo exporter and texinfo
to fix this?
Thanks
Carsten
