RE: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Thank you so much Juan, I could adapt your filter to my needs, and this works
like a charm !
V.
De : Juan Manuel Macías
Envoyé : mardi 25 janvier 2022 18:30
À : Vincent Belaïche
Cc : orgmode
Objet : Re: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Hi Vincent,
Vincent Belaïche writes:
> My conlcusion is that for what I am after, an evolution of org-mode
> would be preferable, maybe I contribute something someday, so that
> writing one of the following would make it:
>
>~--my-option=~\relax{}/option value/
>~--my-option=~@@:@@/option value/
>\left~--my-option=\right~/option value/
>\left~--my-option=\right~\left/option value\right/
>~--my-option=~\left/option value\right/
Considering that Org's emphasis marks are not compromised by contact
with a single quote, I come up with this somewhat dirty solution: you
can use some kind of dummy mark (e.g. two single quotes: '') and put it
between the two emphasis parts. It would then be removed by a filter.
Something like this:
#+BIND: org-export-filter-final-output-functions (my-filter)
#+begin_src emacs-lisp :exports results :results none
(defun my-filter (text backend info)
(replace-regexp-in-string "''" "" text))
#+end_src
~some-cli-option=~''/some cli argument/
== LaTeX ==>
\texttt{some-cli-option=}\emph{some cli argument}
The solution is tricky and temporary, but at least it's not as
text-invasive as other options.
Best regards,
Juan Manuel
RE: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Just replying to myself : the dynamic latin9/utf8 switch does not really easily
work in a LaTeX document (I am sure some people made it work, but I did not
manage to make it).
Adding the ZWSP support is easy, just insert
\DeclareUnicodeCharacter{200B}{}
in the document preamble, but this does not work because the table of content
gets ugly with the titles likes « germe de générateur pseudo-aléatoire »
instead of « germe de générateur pseudo-aléatoire » (some sections in the UTF-8
part going to the toc that is in the latin-9 part).
I tried to circumvent this by using the following encapsulation for the UTF-8
part :
\inputencoding{utf8}\addtocontents{toc}{\protect\inputencoding{utf8}}
...
\inputencoding{latin9}\addtocontents{toc}{\protect\inputencoding{latin9}}
(there are \addtocontents commands in addition to the \inputencoding so that I
also switch the encoding in the toc file), but there are still issues, the
dynamic switch does not work well with moving arguments like section titles
going to the toc file. This is probably a problem of non-immediate write
occurring at page shipout.
V.
De : Vincent Belaïche
Envoyé : mardi 25 janvier 2022 18:18
À : Nicolas Goaziou
Cc : Juan Manuel Macías ; orgmode
Objet : RE: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Hello,
Actually the source was in UTF-8, but it was using only characters that exist
in latin-9, and it is exported to LaTeX for inclusion in a LaTeX document that
is in latin-9.
So I used an Emacs lisp snippet to make the export, and in this snippet after
calling something like (org-export-to-buffer 'latex out-buffer nil nil nil t),
I was doing some insertion like
(goto-char (point-max))
(insert "
% Local Variables:
% coding: latin-9
% End:
")
(save-buffer)
(kill-buffer)
so that the exported buffer is converted to latin-9 before being saved.
OK, when I inserted the zero width space this barked because of no zwsp (aka
U+200B) in latin-9.
Then I tried something else, I rewrote the code with some some LaTeX snippet
@@latex:\kern-0.5em\relax@@ in it, like this:
~--my-option=~ @@latex:\kern-0.5em\relax@@ /option value/
that was OK, but this really makes the OrgMode ugly (maybe a custom entity
would be better), and also this works only for the LaTeX export.
Then, I tried something else, I passed « utf8,latin9 » options, to LaTeX
inputenc package, instead of just « latin9 », and I kept my org mode document
in UTF-8, just before exporting I did something like this in the input buffer:
(goto-char (point-max))
(insert "\n\n#+begin_export latex\n\\inputencoding{latin9}\n#+end_export\n")
(goto-char (point-min))
(insert "\n\n#+begin_export latex\n\\inputencoding{utf8}\n#+end_export\n")
this way the LaTeX processor is switching dynamically from latin9 to utf8 at
the beginning of the doc, and back to latin9 at the end of it. But there are
two pitfalls:
the first one is that zwsp are not defined in the inputenc utf8.def definition
file, so having a zwsp character in the LaTeX code, even though utf8 is
declared as input encoding make a LaTeX compilation error.
the second (but this is less serious I think …) is that my document ends with
an enumerate list, and the orgmode exporter make the second begin_export go
into the enumerate list, not after it. I mean I get in the output this:
\inputencoding{latin9}
\end{enumerate}
instead of this:
\end{enumerate}
\inputencoding{latin9}
My conlcusion is that for what I am after, an evolution of org-mode would be
preferable, maybe I contribute something someday, so that writing one of the
following would make it:
~--my-option=~\relax{}/option value/
~--my-option=~@@:@@/option value/
\left~--my-option=\right~/option value/
\left~--my-option=\right~\left/option value\right/
~--my-option=~\left/option value\right/
De : Nicolas Goaziou
Envoyé : mardi 25 janvier 2022 11:55
À : Vincent Belaïche
Cc : Juan Manuel Macías ; orgmode
Objet : Re: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Hello,
Vincent Belaïche writes:
> Thank-you both for the reply, I should have mentioned that I am aware of
> this trick but it works only for document encodings which have the
> zero-width space, like UTF-8, I was after a fix for documents in
> ISO-8859-15, aka latin-9.
You mean the source itself is not UTF-8?
I don't think there's a solution for you then, unless you convert it to
UTF-8, of course.
Regards,
--
Nicolas Goaziou
RE: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Hello,
Actually the source was in UTF-8, but it was using only characters that exist
in latin-9, and it is exported to LaTeX for inclusion in a LaTeX document that
is in latin-9.
So I used an Emacs lisp snippet to make the export, and in this snippet after
calling something like (org-export-to-buffer 'latex out-buffer nil nil nil t),
I was doing some insertion like
(goto-char (point-max))
(insert "
% Local Variables:
% coding: latin-9
% End:
")
(save-buffer)
(kill-buffer)
so that the exported buffer is converted to latin-9 before being saved.
OK, when I inserted the zero width space this barked because of no zwsp (aka
U+200B) in latin-9.
Then I tried something else, I rewrote the code with some some LaTeX snippet
@@latex:\kern-0.5em\relax@@ in it, like this:
~--my-option=~ @@latex:\kern-0.5em\relax@@ /option value/
that was OK, but this really makes the OrgMode ugly (maybe a custom entity
would be better), and also this works only for the LaTeX export.
Then, I tried something else, I passed « utf8,latin9 » options, to LaTeX
inputenc package, instead of just « latin9 », and I kept my org mode document
in UTF-8, just before exporting I did something like this in the input buffer:
(goto-char (point-max))
(insert "\n\n#+begin_export latex\n\\inputencoding{latin9}\n#+end_export\n")
(goto-char (point-min))
(insert "\n\n#+begin_export latex\n\\inputencoding{utf8}\n#+end_export\n")
this way the LaTeX processor is switching dynamically from latin9 to utf8 at
the beginning of the doc, and back to latin9 at the end of it. But there are
two pitfalls:
the first one is that zwsp are not defined in the inputenc utf8.def definition
file, so having a zwsp character in the LaTeX code, even though utf8 is
declared as input encoding make a LaTeX compilation error.
the second (but this is less serious I think …) is that my document ends with
an enumerate list, and the orgmode exporter make the second begin_export go
into the enumerate list, not after it. I mean I get in the output this:
\inputencoding{latin9}
\end{enumerate}
instead of this:
\end{enumerate}
\inputencoding{latin9}
My conlcusion is that for what I am after, an evolution of org-mode would be
preferable, maybe I contribute something someday, so that writing one of the
following would make it:
~--my-option=~\relax{}/option value/
~--my-option=~@@:@@/option value/
\left~--my-option=\right~/option value/
\left~--my-option=\right~\left/option value\right/
~--my-option=~\left/option value\right/
De : Nicolas Goaziou
Envoyé : mardi 25 janvier 2022 11:55
À : Vincent Belaïche
Cc : Juan Manuel Macías ; orgmode
Objet : Re: [RFC] Creole-style / Support for **emphasis**__within__**a word**
Hello,
Vincent Belaïche writes:
> Thank-you both for the reply, I should have mentioned that I am aware of
> this trick but it works only for document encodings which have the
> zero-width space, like UTF-8, I was after a fix for documents in
> ISO-8859-15, aka latin-9.
You mean the source itself is not UTF-8?
I don't think there's a solution for you then, unless you convert it to
UTF-8, of course.
Regards,
--
Nicolas Goaziou
RE: [O] [RFC] Creole-style / Support for **emphasis**__within__**a word**
Hello,
Thank-you both for the reply, I should have mentioned that I am aware of
this trick but it works only for document encodings which have the
zero-width space, like UTF-8, I was after a fix for documents in
ISO-8859-15, aka latin-9.
V.
De : Juan Manuel Macías
Envoyé : lundi 24 janvier 2022 13:09
À : Vincent Belaïche
Cc : orgmode
Objet : Re: [O] [RFC] Creole-style / Support for **emphasis**__within__**a
word**
Hi Vincent,
Vincent Belaïche writes:
> Hello,
>
> Sorry to dig out this almost 8 year old discussion, but after looking
> into the git HEAD Org Mode manual (v9.5 or so) (info "(org) Emphasis and
> Monospace") node, and after looking into the mail archive I could not
> find any answer to this question: how to switch style within a word.
>
> I would like to put something like this in an OrgMode document:
>
> ~--some-cli-option=~/some cli argument/
>
> where the intent is that « --some-cli-option= » would be monospaced, and
> « some cli argument » would be italicized, and as you know this does not
> work this way.
>
> Vincent.
It seems that this topic is already a classic :-) The supported solution
for intra-word emphases is to introduce a zero width space (U+200B), for
example:
~--some-cli-option=~[zero-width space]/some cli argument/
I don't really like this solution, but at least it works. If you export
to LaTeX, you may want to remove the space using a filter, as in some
(few) cases it can alter the LaTeX result.
The other realistic possibility is to use macros:
{{{mono(--some-cli-option=)}}}{{{emph(some cli argument)}}}
That is, more or less, the state of art. By the nature of its syntax,
emphasis between words is not possible in Org.
Best regards,
Juan Manuel
RE: [O] [RFC] Creole-style / Support for **emphasis**__within__**a word**
Hello, Sorry to dig out this almost 8 year old discussion, but after looking into the git HEAD Org Mode manual (v9.5 or so) (info "(org) Emphasis and Monospace") node, and after looking into the mail archive I could not find any answer to this question: how to switch style within a word. I would like to put something like this in an OrgMode document: ~--some-cli-option=~/some cli argument/ where the intent is that « --some-cli-option= » would be monospaced, and « some cli argument » would be italicized, and as you know this does not work this way. Vincent. De : emacs-orgmode-bounces+vincent.b.1=hotmail...@gnu.org de la part de Jambunathan K Envoyé : dimanche 23 mars 2014 03:59 À : Nicolas Goaziou Cc : emacs-orgmode@gnu.org Objet : Re: [O] [RFC] Creole-style / Support for **emphasis**__within__**a word** Nicolas Goaziou writes: > Good luck. Got my answer. The rest are just details.
Re: [O] info URL « open at point » patch
Hello Eli, Concerning the patch, I understood that you agree with it provided that it is upgraded to mention the change in the etc/NEWS file. So I did that & pushed the change. Concerning your point « Modularity doesn't mean each module must be standalone and self-contained », I agree, and I did not say that there would be anything wrong for e.g. browse-url.el to use a utility function defined elsewhere. Modules are supposed to interact with each other, and that implies that they cannot be fully standalone. However, modulary means that one should observe some functional split: any package, to be called a package, should have in its documentation some terms of reference saying its purpose and listing what functions it accomplishes. While the purpose of the info package is not primarily url manipulation, I had suspected that this sort function was encompassed by the package providing the browse-url function, and that is why I stated that it would be a better modularity if info was relying on a function provided elsewhere --- which indeed is the opposite statement as saying that info has to be standalone and self-contain, and as such re-invent the wheel of url manipulation by itself. Maybe my mistake was however to assume that 'elsewhere' would be best in the same package as that providing 'browse-url', but anyhow, I stand on my point that keeping some URL format specific "\\(?:f\\(?:ile\\|tp\\)\\|https?\\)://" regexp within the the Info-follow-nearest-node is not very good from a modularity point of view. BTW, the 'browse-url-url-at-point' is not documented by a docstring, so can we assume that it is usable outside browse-url ? Anyway, looking at the code I realized that the real work of grabbing the URL is delegated to the thingatpt package, so my suggestion would be that info should also use thingatpt. Probably it would be even better with something like the following construct to remove info URI from those allowed, as they would better be handled from the info browser itself: (let* ((uri-schemes (copy-sequence thing-at-point-uri-schemes)) (info-uri (car-safe (member "info:" uri-schemes))) (thing-at-point-uri-schemes (delq info-uri uri-schemes))) (thing-at-point 'url t)) OK, the info browser does not directly knows about info URL, so some additional work is needed to catch them too. To me this is a real corner case scenario to refer to a document inside a Texinfo docuemnt via an info URL: that would mean the document is available only in info format, ie has not be published in Texinfo. I am not even sure that such document exists. Aren't info URL meant only to refer to info document from document written with something else than Texinfo ? V. De : Eli Zaretskii Envoyé : mardi 26 juin 2018 16:34 À : Vincent Belaïche Cc : emacs-orgmode@gnu.org; brandel...@gmail.com; emacs-de...@gnu.org Objet : Re: info URL « open at point » patch > From: Vincent Belaïche > CC: "emacs-de...@gnu.org" > Date: Tue, 26 Jun 2018 05:47:04 + > > My point is that for a modular design, the same package that provides > the browse-url function, should also provide some match-url-at-point-p > predicate, e.g. There is such a function: browse-url-url-at-point. But in general, I don't agree with your assertion: there's nothing wrong for, e.g., browse-url.el to use a utility function declared somewhere else. Modularity doesn't mean each module must be standalone and self-contained.
Re: [O] info URL « open at point » patch
One more point : do org-mode experts have an idea about whether there are any better way to match a URL that can be browsed with the browse-url function. My point is that for a modular design, the same package that provides the browse-url function, should also provide some match-url-at-point-p predicate, e.g. - 1st optional argument would give a point in the current buffer, (point) if omitted - 2nd optional argument would be an include/exclude list of protocols which you want/don't want to browse with browse-url. All browsable protocols would be assumed if omitted. For instance the info browser would exclude info protocol, so that it can directly browse it. This way the package calling browse-url would be independant/futureproof w.r.t. to URL format/evolultion. V.
Re: [O] info URL « open at point » patch
Just to be factual: 1) Does anybody objects the patch as it is --- if not I would push it to the repo ? 2) Does anybody agrees that the coding of Info-get-token is not futureproof (length of regexp string used for max length of matchable string). Vincent. De : Eli Zaretskii Envoyé : lundi 25 juin 2018 04:30 À : Vincent Belaïche Cc : emacs-de...@gnu.org; emacs-orgmode@gnu.org Objet : Re: info URL « open at point » patch > From: Vincent Belaïche > CC: "emacs-de...@gnu.org" , "emacs-orgmode@gnu.org" > > Date: Sun, 24 Jun 2018 20:34:26 + > > I agree it is a bit strange, but the reason for it is simple : I would > like a single entry point for all the manuals installed on my PC, so > that my old and tired brain does not have to remember where the manual > is located, and what format is it written in. So it would be nice if all > the manuals were just listed in the info top level menu. That's not the strange part. The strange part is to reference an HTML document from a Texinfo document.
Re: [O] info URL « open at point » patch
I agree it is a bit strange, but the reason for it is simple : I would like a single entry point for all the manuals installed on my PC, so that my old and tired brain does not have to remember where the manual is located, and what format is it written in. So it would be nice if all the manuals were just listed in the info top level menu. So, for manuals that are not written in Texinfo and which I have only a PDF, HTML, or whatever, I would like just to create a direntry with an url to the concerned manual. V. De : Eli Zaretskii Envoyé : dimanche 24 juin 2018 20:45 À : Vincent Belaïche Cc : emacs-de...@gnu.org; emacs-orgmode@gnu.org Objet : Re: info URL « open at point » patch > From: Vincent Belaïche > CC: "emacs-de...@gnu.org" , "emacs-orgmode@gnu.org" > > Date: Sun, 24 Jun 2018 18:21:20 + > > What I want to do is to refer an HTML or PDF document from an Info document. > So > I want the info browser to launch the web browser for it to open a > « file: » protocol document. Got it. Strange use case, but whatever.
Re: [O] info URL « open at point » patch
I generated the regexp with (regexp-opt '("ftp" "http" "https"
"file")). I admit that the list of protocols is not clear from the
regexp, but it was already done this way before my change, and I tried
to minimize the change.
More concerning in my opinion is how the Info-get-token is written. As
some point of the code one can read the following statement:
;; First look for a match for START that goes across POS.
(while (and (not (bobp)) (> (point) (- pos (length start)))
(not (looking-at start)))
(forward-char -1))
Here start is a regexp, so (length start) is just the length of the
string holding the regexp, not the max length over which the regexp
match can span. For instance assume that aa is a new new
protocol which you want Info-get-token to catch. This is 10 character
long, but the typical regexp to catch it would be « a\{10\} » which is
only 7 character long.
It would propably be cleaner to provide the value to be used instead of
(length start) as a separate optional argument that would be set to
(length start) if omitted.
Another way would be to have some standard function max-matchable-length
that given some regexp would compute the maximum length of its match (or
output some special value like t if the maximum length is infinite),
thus (length start) could be replaced by (max-matchable-length start)
--- maybe this is already somthing existing. In the same vein there
could be some standard function that given regexp re and some position
pos-in would function position pos-out such that the following
expression would be true:
(save-excursion
(goto-char pos-out)
(and (<= pos-out pos-in)
(looking-at re)
(>= (match-end 0) pos-in)))
I think that such standard function is already existing, but I can't
remember the package name which provides it…
V.
Re: [O] info URL « open at point » patch
See (info "(texinfo) Reference Syntax")… De : Vincent Belaïche Envoyé : dimanche 24 juin 2018 18:48 À : Eli Zaretskii Cc : emacs-de...@gnu.org; emacs-orgmode@gnu.org Objet : RE: info URL « open at point » patch Hello Eli, To my understanding @xref works only for info links (node names or anchors, or qualified thereof where the qualificator is the info document name) --- maybe I am wrong, tell me if so --- but I want to refer to an HTML or PDF document. Vincent. De : Eli Zaretskii Envoyé : dimanche 24 juin 2018 16:31 À : Vincent Belaïche Cc : emacs-de...@gnu.org; emacs-orgmode@gnu.org Objet : Re: info URL « open at point » patch > From: Vincent Belaïche > Date: Sun, 24 Jun 2018 06:57:53 + > > I am writing to both Emacs-devel and org-mode list because this concerns > browsing URL, and Org-mode already has quite some stuff on this. > Recently I came across this that in an Info file a « file: » protocol > URL is not opened at point. Please find attached a patch to make it > known to the Emacs info browser. > My point was that I have some manual that are only in HTML or PDF, like > the SVN manual, In have a local copy, and I want to find it through a > manual index that I written in Texinfo to get an info node with this > index. Maybe I'm missing something, but I don't understand why support for file:// protocol is needed in Info. Info already supports its own protocol of referencing to an external file, via the @xref command and its varieties, with 4 or more arguments. So why cannot you simply use one of those cross-referencing commands, if you want a reference to another manual? Thanks.
Re: [O] info URL « open at point » patch
What I want to do is to refer an HTML or PDF document from an Info document. So
I want the info browser to launch the web browser for it to open a
« file: » protocol document.
Here is the Texinfo source which I would like to use:
--8<8<8<8<8<-- begin -->8>8>8>8>8
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename svnbook.info
@settitle Manuel Subversion 1.8
@c %**end of header
@dircategory Archiving
@direntry
* SVN book: (svnbook). Gestion de versions avec Subversion
@end direntry
@node Top
@top SVN Book
@url{file:///c%3A/Program%20Files/CollabNet/Subversion%20Client/doc/svn-book-html-chunk/index.html,SVN
book}
@bye
@c Lo
cal Variables:
@c compile-command: "makeinfo svnbook.texi && copy svnbook.info
c:\\Nos_Programmes\\MinGW\\msys\\info\\"
@c End:
--8<8<8<8<8<-- end -->8>8>8>8>8
Vincent.
De : Eli Zaretskii
Envoyé : dimanche 24 juin 2018 19:03
À : Vincent Belaïche
Cc : emacs-de...@gnu.org; emacs-orgmode@gnu.org
Objet : Re: info URL « open at point » patch
> From: Vincent Belaïche
> CC: "emacs-de...@gnu.org" , "emacs-orgmode@gnu.org"
>
> Date: Sun, 24 Jun 2018 16:48:30 +
>
> To my understanding @xref works only for info links (node names or anchors,
> or qualified thereof where the
> qualificator is the info document name) --- maybe I am wrong, tell me if so
> --- but I want to refer to an HTML
> or PDF document.
No, Texinfo cross-references work in any format supported by Texinfo.
If your link should only appear in the HTML version, you could use the
@ifhtml..@end ifhtml conditional, and similarly with links that should
only appear in PDF (i.e. printed version) of the manual. There's also
@ifnotinfo etc.
So once again I don't think I understand the problem. Could you
perhaps elaborate, or show an actual example?
[O] info URL « open at point » patch
Bonjour tout l'monde ! I am writing to both Emacs-devel and org-mode list because this concerns browsing URL, and Org-mode already has quite some stuff on this. Recently I came across this that in an Info file a « file: » protocol URL is not opened at point. Please find attached a patch to make it known to the Emacs info browser. My point was that I have some manual that are only in HTML or PDF, like the SVN manual, In have a local copy, and I want to find it through a manual index that I written in Texinfo to get an info node with this index. I suspect that some other people than me may have the same need, and as such the patch is useful. If everybody agrees with the attached patch I can commit/push it on the master branch. Now, maybe it is the time to reconsider how the info browser consider URL's, maybe there is some code factorization to do with org-mode, in order to accept a wider range of variety of URL's. Org-mode is good at that, and that is why I am having its forum in the loop of this discussion. For instance, I remember that at some point of time at my job I was handling some requirements with IBM-Doors (it was a long time ago, and that SW was named Telelogic-Doors at that time). I had a few org-mode files with custom URL's pointing at Doors objects, and that was quite useful to me to be able to keep in my TODO lists, and other Org-mode stuff direct links to these objects. I suspect that some people may have the same need with Texinfo documents when they want to use custom URL's… Vincent. info-patch.diff Description: info-patch.diff
Re: [O] info URL « open at point » patch
Hello Eli, To my understanding @xref works only for info links (node names or anchors, or qualified thereof where the qualificator is the info document name) --- maybe I am wrong, tell me if so --- but I want to refer to an HTML or PDF document. Vincent. De : Eli Zaretskii Envoyé : dimanche 24 juin 2018 16:31 À : Vincent Belaïche Cc : emacs-de...@gnu.org; emacs-orgmode@gnu.org Objet : Re: info URL « open at point » patch > From: Vincent Belaïche > Date: Sun, 24 Jun 2018 06:57:53 + > > I am writing to both Emacs-devel and org-mode list because this concerns > browsing URL, and Org-mode already has quite some stuff on this. > Recently I came across this that in an Info file a « file: » protocol > URL is not opened at point. Please find attached a patch to make it > known to the Emacs info browser. > My point was that I have some manual that are only in HTML or PDF, like > the SVN manual, In have a local copy, and I want to find it through a > manual index that I written in Texinfo to get an info node with this > index. Maybe I'm missing something, but I don't understand why support for file:// protocol is needed in Info. Info already supports its own protocol of referencing to an external file, via the @xref command and its varieties, with 4 or more arguments. So why cannot you simply use one of those cross-referencing commands, if you want a reference to another manual? Thanks.
Re: [O] Patch on org-read-property-name
Applied, thanks a lot. -- Bastien You're welcome, Vincent.
[O] Patch on org-read-property-name
Hello, Please find a patch for setting properties. A name is proposed when the pointer is on a property line, the name in that line is set as default. Changelog: --- 2011-06-22 Vincent Belaïche vincen...@users.sourceforge.net * org.el (org-read-property-name): Propose default proerty name value by looking at whether current line is already some property setting. --- diff --git a/lisp/org.el b/lisp/org.el index b1edfa3..8318968 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -6591,7 +6591,7 @@ in an indirect buffer, in overview mode. You can dive into the tree in that copy, use org-occur and incremental search to find a location. When pressing RET or `Q', the command returns to the original buffer in which the visibility is still unchanged. After RET is will also jump to -the location selected in the indirect buffer and expose the headline +the location selected in the indirect buffer and expose the headline hierarchy above. (interactive P) (let* ((org-refile-targets `((nil . (:maxlevel . ,org-goto-max-level @@ -14095,7 +14095,20 @@ This is computed according to `org-property-set-functions-alist'. Read a property name. (let* ((completion-ignore-case t) (keys (org-buffer-property-keys nil t t)) - (property (org-icompleting-read Property: (mapcar 'list keys + (default-prop (save-excursion + (save-match-data + (beginning-of-line) + (and (looking-at ^\\s-*:\\([^:\n]+\\):) +(null (string= (match-string 1) END)) +(match-string 1) + (property (org-icompleting-read + (concat Property + (if default-prop (concat [ default-prop ]) ) + : ) + (mapcar 'list keys) + nil nil nil nil + default-prop + ))) (if (member property keys) property (or (cdr (assoc (downcase property) @@ -16120,7 +16133,7 @@ sequence appearing also before point. Even though the matchers for math are configurable, this function assumes that \\begin, \\(, \\[, and $$ are always used. Only the single dollar delimiters are skipped when they have been removed by customization. -The return value is nil, or a cons cell with the delimiter and the +The return value is nil, or a cons cell with the delimiter and the position of this delimiter. This function does a reasonably good job, but can locally be fooled by
[O] RE: Alinea filling (hanlding of explicit line-breaks)
Date: Sat, 12 Mar 2011 22:41:02 + From: k...@freefriends.org To: vincent@hotmail.fr CC: monn...@iro.umontreal.ca; emacs-de...@gnu.org Subject: RE: Alinea filling (hanlding of explicit line-breaks) [...] 1. Sure, @* forces a line break in Texinfo. How that technically compares to \\ in org mode, I don't know. [...] FYI, the only --- but significative --- difference is that in Org \\ needs to be placed at end of line to be active. This is the reason why it is quite disturbing in Org if the paragraph filling moves \\ from the end of of line. In Texinfo it is rather a matter of taste whether you like it or not that in the source code @* are also at end of line to look like the output --- I personally like it this way. VBR, Vincent.
[O] RE: Alinea filling (hanlding of explicit line-breaks)
Salut Stéfan, Actually, no, because paragraph-separate would cause the whole line that ends with \\ to be treated as not being part of a paragraph, and paragraph-start wouldn't be appropriate either. Hence the good above :-( [...] I have implemented the thing locally on my machine. It works well but there is still something missing: the line containing the `\\' alinea separtor is not filled. As you can see above, I'm not surprised. Just don't use paragraph-separate. What I'd do is to use a fill-forward-paragraph-function which calls forward-paragraph, then searches for a $ between the start and end point, and if found adjust the end result accordingly. If/when you come up with this function, please submit for inclusion in tex-mode.el where it will come in handy as well. So, after more thinking about it the problem is the following: the fill-forward-paragraph has only one parameter which is the paragraph number --- with n = 0 = current --- but for finding the paragraph boundary we need *two* parameter = 1st argument: paragraph number = 2nd argument: whether we want to point at the beginning the paragraph or to the end of the paragraph. AFAIK the sign of the argument gives you this information. Oh, I had missed that. The docstring of forward-paragraph is not very clear about that. So, I understand you as follows: basically when you are in the middle of a paragraph, then -1 and +1 both mean current paragraph, with -1 meaning beginning of paragraph and and +1 meaning end of paragraph. But it seems that it does not exactly does the job this way: if the argument sign is 0 and you are in the middle of a paragraph, then, unless the paragraph is at beginning of buffer you are going to the character before the 1st one, rather than to the 1st character of paragraph. So, it seems that you are indeed going to and end of paragraph with arg 0, but that with arg 0, the what happens is more fuzzy. = maybe paragraph-separate could be a list of 3 items (REGEXP BEG END) where REGEXP is the usual regexp matching the separator, and BEG and END when non nil are function to go the the beginning of next or to the end of previous assuming that the match data corresponds to a match of REGEXP. This way would be really the most flexible. Could be, but once you're in fill-forward-paragraph-function, you can do it by hand with Elisp code, so it's not that important. If/when we have enough fill-forward-paragraph-functions we may revisit this opinion, but I don't think we have enough experience yet to make a good design. You are right, this can be done by implementing fill-forward-paragraph-function accordingly. My idea was just to use the same forward-paragraph engine for paragraph motion and for paragraph filling, so the fill-forward-paragraph-function would just have been some wrapper to call forward-paragraph with the correct parameters for filling. Now, I am a bit confused about what should be the correct behaviour of the fill-forward-paragraph-function: is that the following: - arg 0: goto beginning of paragraph arg+1, with paragraph 0 = current - arg 0 : goto beginning of paragraph arg-1, with paragraph 0 = current Where: - beginning = point to 1st character of paragraph, - end = point to next character to last character of paragraph (typically the `\n' at the end of paragraph is part of this paragraph). Stefan Vincent.
[O] RE: Alinea filling (hanlding of explicit line-breaks)
Karl: I put you in the loop for info, because in Texinfo mode I think that @* is used as an alinea separator similar to \\ in Org mode. From: monn...@iro.umontreal.ca To: vincent@hotmail.fr Date: Wed, 16 Feb 2011 10:02:37 -0500 CC: emacs-orgmode@gnu.org; emacs-de...@gnu.org Subject: Re: Alinea filling (hanlding of explicit line-breaks) An important question here is: is it important for M-} to ignore those \\? I guess so, this is the current default Org behaviour anyhow. Good. as far as I understand, it would be anyhow possible to move point on an alinea-by-alinea basis just by configuring the tailing \\ as anohter paragraph separator. Actually, no, because paragraph-separate would cause the whole line that ends with \\ to be treated as not being part of a paragraph, and paragraph-start wouldn't be appropriate either. Hence the good above :-( Of course fill-paragraph-function sucks because it only applies to fill-paragraph and not to fill-region. Do you mean that `fill-paragraph-function' is some kind of obsolete feature and that people should use another kind of hook, and if so which one? Yes and no: there is no replacement for it. There is fill-forward-paragraph-function, which can handle some of the cases for which fill-paragraph-function has been used, but there would need to be something like a fill-region-as-paragraph-function and we don't have that yet :-( Stefan Hello Stefan al, I have implemented the thing locally on my machine. It works well but there is still something missing: the line containing the `\\' alinea separtor is not filled. Here is what I did: + In org-set-autofill-regexps function I added (org-set-local 'fill-forward-paragraph-function 'org-fill-foward-paragraph) + I created the following function: (defun org-fill-foward-paragraph (optional arg) (let ((paragraph-separate (concat .*$\\| paragraph-separate ))) (forward-paragraph arg))) Note that I my 7.01h version of org --- which is older than the latest one --- org-fill-paragraph is roughly like this: (defun org-fill-paragraph (optional justify) Re-align a table, pass through to fill-paragraph if no table. (let ((table-p (org-at-table-p)) (table.el-p (org-at-table.el-p))) (cond ((and (equal (char-after (point-at-bol)) ?*) (save-excursion (goto-char (point-at-bol)) (looking-at outline-regexp))) t); skip headlines (table.el-p t) ; skip table.el tables (table-p (org-table-align) t) ; align org-mode tables (t nil); let fill.el do the job ))) That is to say there is a case where org lets fill.el do the job, while in a later version (e.g. 7.4) org does some $ detection on its own without the use of the fill-forward-paragraph-function. So, after more thinking about it the problem is the following: the fill-forward-paragraph has only one parameter which is the paragraph number --- with n = 0 = current --- but for finding the paragraph boundary we need *two* parameter = 1st argument: paragraph number = 2nd argument: whether we want to point at the beginning the paragraph or to the end of the paragraph. = maybe paragraph-separate could be a list of 3 items (REGEXP BEG END) where REGEXP is the usual regexp matching the separator, and BEG and END when non nil are function to go the the beginning of next or to the end of previous assuming that the match data corresponds to a match of REGEXP. This way would be really the most flexible. VBR, Vincent
[Orgmode] Re: Alinea filling (hanlding of explicit line-breaks)
Maybe an example is better to explain what I need, imagine that I have the following two paragraphs: [...] Where I assumed that alineas are separated by either an empty line or a tailing `\\' while paragraphs are separated by just an empty line. An important question here is: is it important for M-} to ignore those \\? I guess so, this is the current default Org behaviour anyhow. as far as I understand, it would be anyhow possible to move point on an alinea-by-alinea basis just by configuring the tailing \\ as anohter paragraph separator. I usually use alinea as follows: --- John Foo (2011-02-16T07:36:02) said:\\ blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah Mikaël Bar (2011-02-15T16:28:16) said:\\ gronk gronk gronk gronk gronk gronk gronk gronk gronk gronk gronk gronk gronk gronk gronk gronk --- I don't want M-} to recognize alineas as separate paragraphs because the first alinea of each paragraph is just one line. [...] Of course fill-paragraph-function sucks because it only applies to fill-paragraph and not to fill-region. Do you mean that `fill-paragraph-function' is some kind of obsolete feature and that people should use another kind of hook, and if so which one? [...] Stefan Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Alinea filling (hanlding of explicit line-breaks)
Hi, Good to see that I am not the only one needing that sort of things. Maybe an example is better to explain what I need, imagine that I have the following two paragraphs: --- aaa a aaa a aaa a a a aaa a aa a aaa aaa aa a a a aa a a aaa a aa a a aa a aaa aa aa aaa a aa a aaa a aaa aaa a aaa a a aaa aaa a a a aa a aaa aa a aaa a a aaa a a a a a aa aaa aaa aa a a a aaa aaa a aa a aa aaa a a\\ bbb b bbb b bbb b b b bbb b bb b bbb bbb bb b b b bb b b bbb b bb b b bb b bbb bb bb bbb b bb b bbb b bbb bbb b bbb b b bbb bbb b b b bb b bbb bb b bbb b b bbb b b b b b bb bbb bbb bb b b b bbb bbb b bb b bb bbb b b ccc c ccc c ccc c c c ccc c cc c ccc ccc cc c c c cc c c ccc c cc c c cc c ccc cc cc ccc c cc c ccc c ccc ccc c ccc c c ccc ccc c c c cc c ccc cc c ccc c c ccc c c c c c cc ccc ccc cc c c c ccc ccc c cc c cc ccc c c\\ ddd d ddd d ddd d d d ddd d dd d ddd ddd dd d d d dd d d ddd d dd d d dd d ddd dd dd ddd d dd d ddd d ddd ddd d ddd d d ddd ddd d d d dd d ddd dd d ddd d d ddd d d d d d dd ddd ddd dd d d d ddd ddd d dd d dd ddd d d --- after filling I wish that it would become --- aaa a aaa a aaa a a a aaa a aa a aaa aaa aa a a a aa a a aaa a aa a a aa a aaa aa aa aaa a aa a aaa a aaa aaa a aaa a a aaa aaa a a a aa a aaa aa a aaa a a aaa a a a a a aa aaa aaa aa a a a aaa aaa a aa a aa aaa a a\\ bbb b bbb b bbb b b b bbb b bb b bbb bbb bb b b b bb b b bbb b bb b b bb b bbb bb bb bbb b bb b bbb b bbb bbb b bbb b b bbb bbb b b b bb b bbb bb b bbb b b bbb b b b b b bb bbb bbb bb b b b bbb bbb b bb b bb bbb b b ccc c ccc c ccc c c c ccc c cc c ccc ccc cc c c c cc c c ccc c cc c c cc c ccc cc cc ccc c cc c ccc c ccc ccc c ccc c c ccc ccc c c c cc c ccc cc c ccc c c ccc c c c c c cc ccc ccc cc c c c ccc ccc c cc c cc ccc c c\\ ddd d ddd d ddd d d d ddd d dd d ddd ddd dd d d d dd d d ddd d dd d d dd d ddd dd dd ddd d dd d ddd d ddd ddd d ddd d d ddd ddd d d d dd d ddd dd d ddd d d ddd d d d d d dd ddd ddd dd d d d ddd ddd d dd d dd ddd d d --- Where I assumed that alineas are separated by either an empty line or a tailing `\\' while paragraphs are separated by just an empty line. What you say (making distinct separation of paragraph for motion and of fillable-region) is more than what I needed, because I assumed that alineas and paragraphs are not completely separate things, as an alinea is always a subset of a paragraph. Concerning EUPP, after more thinking, I realized that alineas are not the good approach: actually I don't need any special filling but rather to disable filling in some occasions, and for that using the fill-paragraph-function is a better approach. So, for Org I will just install emacs-24 --- or at least the fill package, is it backward compatible with an emacs-23 ? Thanks for the feedback, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list.
[Orgmode] Alinea filling (hanlding of explicit line-breaks)
Dear all, I would like to suggest an evolution of fill.el. I can make the update and provide the diff file. The proposal is to add, in addition to paragraph separator, an alinea separator. Accordingly there would be a forward-alinea function similar to forward-paragraph. An alinea is, in French regulatory jargon, (er, what is the English word for alinea? ) a part in a paragraph that is separated by a line break, and typically starting with an indentation. Not all pargraphs are separated into alineas. That evolution would be completely backward compatible: with a nil alinea separator, the behaviour would be same as the current one, and otherwise paragraph filling would fill each alineas within the current paragraph as if they were paragraphs on their owns. I felt the need for this in two occasions, the first one was for EUPP (cf http://vincentbelaiche.pagesperso-orange.fr/#sec-1_2), and the second one was with Org mode. EUPP embeds lisp code into comments thanks to special markup added onto the usual comment marks. With EUPP, I needed to prevent the paragraph filling to mangle those comment extra marks, as otherwise they would be erroneously separated from normal comment marks. One solution would be that the EUPP mark that is at each end of line of embedded lisp code is configured as an alinea separator. I suggested an evolution on AUCTeX (as I use EUPP mostly in conjunction with LaTeX code), but the answer from Ralf Angeli at that time was that this should rather be an evolution of generic filling service in fill.el, and I was convinced by him that this would be a better way. Another occasion, is for Org mode. In Org-mode: the explicit line break is a `\\' placed at end of line. If `\\' is not at end of line it loses its meaning of line-break. Filling a paragraph that contains an explicit line break is quite a disturbance because most often the line tailing \\ is moved and as after filling it is no longer at the end of line, it loses its linebreaking power. The solution would be to configure `$' into the alinea separator, so that filling a paragraph does not mix alineas together. Feedback to this proposal is most welcome, in case that there is a consensus on the usefulness of alinea separation, I would provide the updated code/bazaar diff. VBR, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] Export issue of URL when the text begins with a date
Date: Sat, 15 Jan 2011 07:40:35 +0100 From: dm...@ictsoc.de To: vincent@hotmail.fr Subject: Re: [Orgmode] Export issue of URL when the text begins with a date CC: dm...@ictsoc.de; emacs-orgmode@gnu.org At Fri, 14 Jan 2011 22:12:07 +0100, Vincent Belaïche wrote: Thank-you David again for carrying out this correction. By the way, I noticed in the source tree that has a test base, that there is some testing sub-directory. I was expecting that there would be a list of testNN.org testNN.tex testNN.html etc... so that to check that to carry out non regression tests from testNN.org exported to reference testNN.tex and testNN.html. It seems that such a non-regression test base and script do not exist. However that would be good to have in order to check that any correction does not break anything. That's exactly what the testing framework[1] could and should do. I've just not figured out how to best write tests for entire export operations. Thinking of it: We could create an input file dedicated to test link exporting, put in different kinds of links, export and then use regexps to check if the links have been exported fine. Best, -- David [...] Hello David and al., I sketched some test script, herein attached. It allows to make a few export tests. I hope that this is what you had in view... Vincent. test-export.el Description: application/emacs-lisp ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] Doors links
Date: Fri, 14 Jan 2011 23:18:21 +0100
From: m...@christianmoe.com
To: emacs-orgmode@gnu.org
Subject: Re: [Orgmode] Doors links
Hi,
Try these:
[[info:org:Link abbreviations]]
[[info:org:Adding%20hyperlink%20types][info:org:Adding hyperlink types]]
Yours,
Christian
[...]
Thanks, I will try that ! I think that the trick deserves a forward link
in the documentation. I made a patch to the doc, attached.
Vincent.
diff --git a/doc/org.texi b/doc/org.texi
index 4d696ae..96e2e50 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -3093,6 +3093,8 @@ elisp:org-agenda @r{Interactive Elisp command}
elisp:(find-file-other-frame Elisp.org) @r{Elisp form to evaluate}
@end example
+For customizing Org to add new link types @ref{Adding hyperlink types}.
+
A link should be enclosed in double brackets and may contain a
descriptive text to be displayed instead of the URL (@pxref{Link
format}), for example:
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Doors links
Hello, I use Org also at my job to write some short reports. These reports may contains URLs to Doors objects. Doors is a paying S/W to manage a requirement data base --- this is used in the industry for writing complex specification documents where each clause has to be tracked like a separate object. Doors URLs are not properly exported to HTML by Org. for instance: [[doors:foo/bar/gnats][machin truc]] exports to a href=#doors:foo/bar/gnatsmachin truc/a but I would have prefered a href=doors:foo/bar/gnatsmachin truc/a Is there any way to configure Org to do the job properly (like some hook URL processing hook), I could not find anything in the documentation. VBR, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] Export issue of URL when the text begins with a date
[...] My understanding is that the bug resides in this very expression. Thanks for the investigation. As it turned out the problem was not with the regular expression but with the order in which different pieces of Org mode markup were processed by `org-export-as-html'. First the exporter processed possible timestamps, (falsely) recognized the ISO date as part of an ISO timestamp, and replaced it with the timestamp span. The replacement included the square brackets what destroyed the link markup. I've just checked in a patch to master that changes the order of processing links and timestamps: Now links are processed before timestamps what fixes this problem. Thanks for bringing this problem up again, Best, -- David -- [...] Thank-you David again for carrying out this correction. By the way, I noticed in the source tree that has a test base, that there is some testing sub-directory. I was expecting that there would be a list of testNN.org testNN.tex testNN.html etc... so that to check that to carry out non regression tests from testNN.org exported to reference testNN.tex and testNN.html. It seems that such a non-regression test base and script do not exist. However that would be good to have in order to check that any correction does not break anything. Is that something that is considered for future ? Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [Emacs-orgmode] cannot store link to an info ode?
Hello, I am restarting this very old thread: http://lists.gnu.org/archive/html/emacs-orgmode/2006-05/msg00121.html see also http://lists.gnu.org/archive/html/emacs-orgmode/2010-12/msg01229.html I realized that `M-x org-store-link' does now work with info nodes, and that the info nodes links are correctly followed and documented. The link format is like this: [[info:org.info:External%20links][some description]] This format contradicts the assumption made in the URL package, according to URL documentation the format should have been [[info:org.info#External%20links][some description]] i.e. the second colon is a sharp instead. I am not saying that URL is correct and org wrong, but at least there should be something done for ensuring compatibility (like asking URL maintainer to support also Org format, or implementing also the URL format in org) I am also wondering why Org did not align on the convention made by URL which seems to be earlier. Finally I make again the same suggestion, it would be good to have also a line pointer, especially as it seems that the latest version of info also have a line pointer in the index nodes. VBR, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Export issue of URL when the text begins with a date
Hello, I have made some invesitgation, and I found that the problem happens in the call of function org-export-as-html. On line 522 of this function, this is the following line: (while (string-match org-bracket-link-analytic-regexp++ line start) When the line containing the link is processed, the variable line is equal to the following [[file://localhost/c%3A/msys/1.0/temp/example.html][2011-01-01 example]] In that case the expression (string-match org-bracket-link-analytic-regexp++ line start) returns nil. Now assume that I modify slightly the line so that there is not longer any ISO timestamp in it, like this (I just replaced the first `-' by a `+', so the string is : [[file://localhost/c%3A/msys/1.0/temp/example.html][2011+01-01 example]] ) with that change the expression (string-match org-bracket-link-analytic-regexp++ line start) returns 0. My understanding is that the bug resides in this very expression. VBR, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Export issue of URL when the text begins with a date
Hello, Here is an example org file: --- * some example [[file://localhost/c%3A/msys/1.0/temp/example.html][2011-01-01 example]] --- When I export this with `C-c C-e h' I get the following in place of the URL: --- p [[file://localhost/c%3A/msys/1.0/temp/example.html] span class=timestamp-wrapper span class=timestamp2011-01-01 example/span/span] /p --- I would have rather expected something like --- a href=file://localhost/c%3A/msys/1.0/temp/example.html2011-01-01 example/a --- BTW: happy new year 2011 to all ! Vincent. Hello, I could not see any feedback. Am I the only one with this issue. Shall I fill in a bug report ? Vincent. PS: I have tried again with the laster on the Git repo, and the problem is still there. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Export issue of URL when the text begins with a date
Hello, Here is an example org file: --- * some example [[file://localhost/c%3A/msys/1.0/temp/example.html][2011-01-01 example]] --- When I export this with `C-c C-e h' I get the following in place of the URL: --- p [[file://localhost/c%3A/msys/1.0/temp/example.html] span class=timestamp-wrapper span class=timestamp2011-01-01 example/span/span] /p --- I would have rather expected something like --- a href=file://localhost/c%3A/msys/1.0/temp/example.html2011-01-01 example/a --- BTW: happy new year 2011 to all ! Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] %20 in file://... URL
[...] hoping that the above helps. Definitely. Last not least: On this mailing list you should normally Cc: answers to the original poster -- some are not subscribed to the list at all, some (like me) read the list in a different account than their main mail account and miss answers etc. Best and thanks, -- David By the way, I realized that emacs embeds a URL package that already has some URL parse function url-generic-parse-url. Wouldn't it be better if Org would just rely on this function and/or extend it, or at least if org would offer the same API as url and try to align on the same conventions for non standard URL's, so that org could be a replacement to the URL package. I noticed that the URL package does not seem to make any %XX decoding, for instance on my machine: (url-generic-parse-url file:c%3A/toto.html) evaluates to [cl-struct-url file nil nil nil 21 c%3A/toto.html nil nil nil] I also noticed that the info:FILE#NODE does not seem to be supported by Org, but it is by URL. Actually it would be even more useful to have also info:FILE#NODE::NNN with NNN being the line number within the info NODE, but url does not support the ::NNN extension which seems to be defined only in Org. VBR, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Export of quoted region to HTML
Hello, In the following: --- * grmag, #+begin_quote flkan mvrj: + vfdeovndeq vdQ GV DRGB RGH RF HR H RH TR HTR HTZNTS FEZ GFE GEGERBGER EGAGEG FEZ AGG ERG R GHRA + fe zf el eaglv erg rbg ergnr brpa bgrek bgrekbg rekbg er gver^gn EMGF EMERGVJ DEKM ERE GVBV VGLEELER #+end_quote --- The quoted part get exported to HTML as: --- blockquote pflkan mvrj: /pul li vfdeovndeq vdQ GV DRGB RGH RF HR H RH TR HTR HTZNTS FEZ GFE GEGERBGER EGAGEG FEZ AGG ERG R GHRA /li li fe zf el eaglv erg rbg ergnr brpa bgrek bgrekbg rekbg er gversupgn/sup EMGF EMERGVJ DEKM ERE GVBV VGLEELER /blockquote --- The /li/ul closure is missing. Is that a bug? Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] %20 in file://... URL
Date: Wed, 17 Nov 2010 21:43:59 +0100 From: dm...@ictsoc.de To: vincent@hotmail.fr Subject: Re: [Orgmode] %20 in file://... URL CC: emacs-orgmode@gnu.org; carsten.domi...@gmail.com [...] Hello, Sorry for the delay, I was on business trip. Thanks for sending the patch, but it won't provide a clean solution to the problem: The function modified by your patch works under the assumption, that for example the sequence %3A represents a percent escaped colon. But the function that creates the link in the first place does not percent-escape chars Er, in my situation I create the link with another package, and I *did* escaped the colon. -- If we use just this patch, opening a link to a file literarally called %3A.org will fail. So we need to modify all functions that create links to propertly percent-escape the part of a link that follows the link type in order to make all functions unescape the link. Good news: Reworking the percent-escaping is a work in progress on my list[1] and if it is finished and accepted, the problem should be solved. Best, -- David I see, so I understand that you will someday modify a function creating links in order to implement character escaping. I can give a hand if tell me the function name. I also send you my patch with a git diff, just in case (with same changelog attached again). Sorry for using `diff -c', I just followed the info node `(emacs) Sending Patches' Vincent. diff --git a/lisp/org.el b/lisp/org.el index 201dd87..4e2e2c4 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -9639,9 +9639,28 @@ to search for. If LINE or SEARCH is given, the file will be opened in Emacs, unless an entry from org-file-apps that makes use of groups in a regexp matches. If the file does not exist, an error is thrown. - (let* ((file (if (equal path ) + (let* ((%xx-decoded-path + (let ((pos 0) (%xx-decoded-path path)) + (setq %xx-decoded-path path) + (while (setq pos (string-match %\\([0-9A-F]\\)\\([0-9A-F]\\) %xx-decoded-path pos)) + (setq pos (1+ pos) + %xx-decoded-path (replace-match + (string (let ((code 0) digit) + (dotimes (i 2) + (setq + digit (aref (match-string (1+ i) %xx-decoded-path) 0) + code (+ (if (= digit ?9) + (- digit ?0) + (- digit 55)) + (* 16 code code)) + t t %xx-decoded-path))) + ;; remove //localhost/ prefix if any + (and (string-match \\`//localhost/ %xx-decoded-path) + (setq %xx-decoded-path (substring %xx-decoded-path 12))) + %xx-decoded-path)) + (file (if (equal path ) buffer-file-name - (substitute-in-file-name (expand-file-name path + (substitute-in-file-name (expand-file-name %xx-decoded-path (file-apps (append org-file-apps (org-default-apps))) (apps (org-remove-if 'org-file-apps-entry-match-against-dlink-p file-apps)) 2010-11-13 Vincent Belaïche vincen...@users.sourceforge.net * org.el (org-open-file): Decode %XX escapes in URL with file type, so that applications other than browsers are not confused with the filename. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] %20 in file://... URL
Date: Wed, 17 Nov 2010 21:43:59 +0100 From: dm...@ictsoc.de To: vincent@hotmail.fr Subject: Re: [Orgmode] %20 in file://... URL CC: emacs-orgmode@gnu.org; carsten.domi...@gmail.com [...] Hello, Sorry for the delay, I was on business trip. Thanks for sending the patch, but it won't provide a clean solution to the problem: The function modified by your patch works under the assumption, that for example the sequence %3A represents a percent escaped colon. But the function that creates the link in the first place does not percent-escape chars Er, in my situation I create the link with another package, and I *did* escaped the colon. -- If we use just this patch, opening a link to a file literarally called %3A.org will fail. So we need to modify all functions that create links to propertly percent-escape the part of a link that follows the link type in order to make all functions unescape the link. Good news: Reworking the percent-escaping is a work in progress on my list[1] and if it is finished and accepted, the problem should be solved. Best, -- David I see, so I understand that you will someday modify a function creating links in order to implement character escaping. I can give a hand if tell me the function name. I also send you my patch with a git diff, just in case (with same changelog attached again). Sorry for using `diff -c', I just followed the info node `(emacs) Sending Patches' Vincent. diff --git a/lisp/org.el b/lisp/org.el index 201dd87..4e2e2c4 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -9639,9 +9639,28 @@ to search for. If LINE or SEARCH is given, the file will be opened in Emacs, unless an entry from org-file-apps that makes use of groups in a regexp matches. If the file does not exist, an error is thrown. - (let* ((file (if (equal path ) + (let* ((%xx-decoded-path + (let ((pos 0) (%xx-decoded-path path)) + (setq %xx-decoded-path path) + (while (setq pos (string-match %\\([0-9A-F]\\)\\([0-9A-F]\\) %xx-decoded-path pos)) + (setq pos (1+ pos) + %xx-decoded-path (replace-match + (string (let ((code 0) digit) + (dotimes (i 2) + (setq + digit (aref (match-string (1+ i) %xx-decoded-path) 0) + code (+ (if (= digit ?9) + (- digit ?0) + (- digit 55)) + (* 16 code code)) + t t %xx-decoded-path))) + ;; remove //localhost/ prefix if any + (and (string-match \\`//localhost/ %xx-decoded-path) + (setq %xx-decoded-path (substring %xx-decoded-path 12))) + %xx-decoded-path)) + (file (if (equal path ) buffer-file-name - (substitute-in-file-name (expand-file-name path + (substitute-in-file-name (expand-file-name %xx-decoded-path (file-apps (append org-file-apps (org-default-apps))) (apps (org-remove-if 'org-file-apps-entry-match-against-dlink-p file-apps)) 2010-11-13 Vincent Belaïche vincen...@users.sourceforge.net * org.el (org-open-file): Decode %XX escapes in URL with file type, so that applications other than browsers are not confused with the filename. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] %20 in file://... URL
From: David Maus Subject: Re: [Orgmode] %20 in file://... URL Date: Mon, 22 Nov 2010 19:16:09 +0100 User-agent:Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (GojÅ) APEL/10.8 Emacs/23.2 (i486-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) At Mon, 22 Nov 2010 16:46:44 +0100, Vincent Belaïche wrote: I see, so I understand that you will someday modify a function creating links in order to implement character escaping. I can give a hand if tell me the function name. To be exact: Org already escapes some characters (C-h v org-link-escape-chars RET) and the colon is a candidate for beeing on the list. What does already exactly means ? I pushed the colon '(?: . %3A) into this org-link-escape-chars list, and I made a trial with a link like this: [[file://localhost/c%3A/msys/1.0/temp/jay.html][link]] I get this message: if: No such file: //localhost/c%3A/msys/1.0/temp/jay.html, evaluating the full org.el on the link you gave does not make it either because I get the message that org-complete cannot be loaded. The functions responsible for escaping/unescaping are `org-link-escape' and `org-link-unescape' and the new implementations of these functions can be found in https://github.com/dmj/dmj-org-mode/tree/feature/org-percent-escaping Ok, you mean that some version of org already does the job, but not the org that is on the official Git depo ? The task at hand: Anticipate the consquences of the new implementation. I.e. what will happen to links created with the old algorithm. I have no idea of the consequences, I can be a beta tester of it, but for the time being this code does not work with the kind of link which I use. Patches, ideas, and comments on the modifications are welcome. The following is just comments on the code, most of it is a matter of taste, which you may well disagree with. 1. In the org.el file in the link which you provided I found also these functions org-entry-protect-space org-entry-restore-space which does also some escaping, why not use a unique function 2. In the function org-link-escape, there is a lambda expression (lambda (sequence) (format %%%.2X sequence)) The argument name should be sequence-element rather than sequence. 3. In org-link-unescape, there are 3 substringing-or-concatenations, but you could make it simpler by a single replace-match and using a start-position in the string-match. That would look like this (*not tested*): (defun org-link-unescape (str) Unhex hexified unicode strings as returned from the JavaScript function encodeURIComponent. E.g. `%C3%B6' is the german Umlaut `ö'. (setq str (or str )) (let ((case-fold-search t) (pos 0)) (while (string-match \\(%[0-9a-f][0-9a-f]\\)+ str pos) (setq pos (+ pos (/ (- (match-end 0) (match-beginning 0)) 3)) str (replace-match (org-link-unescape-compound (upcase (match-string 0 str); hex )) t t str str)) My feeling that the kind of code above is slightly simpler in execution as there is only one string manipulation at each iteration instead of two, and also easier to maintain as is has fewer use cases (i.e. it does not really matter if the escaped sequence is at the end of string or not). You also avoid some intermediate variables like `replacement' as the use of replace-match make it self explanatory that the result of org-link-unescape-compound is a replacement. 3. in org-link-unescape-compound, (remove (split-string hex %)) can be replaced by (cdr (split-string hex %)) because there is always only one empty string in the sequence and it is in the 1st place. 4. in org-link-unescape-compound, you could have made fewer comparison by replacing code (shift (if (= 0 eat) ;; new byte (if (= val 252) 6 (if (= val 248) 5 (if (= val 240) 4 (if (= val 224) 3 (if (= val 192) 2 0) 6)) (xor (if (= 0 eat) ;; new byte (if (= val 252) 252 (if (= val 248) 248 (if (= val 240) 240 (if (= val 224) 224 (if (= val 192) 192 0) 128))) by (*not tested*): (shift-xor (if (= 0 eat) ;; new byte (if (= val 252) '(6 . 252) (if (= val 248) '(5 . 248) (if (= val 240) '(4 . 240) (if (= val 224) '(3 . 224) (if (= val 192) '(2 . 192) '(0. 0)) '(6 . 128))) (shift (car shift-xor)) (xor (cdr shift-xor)) the code above looks more concise to me, depending on val
Re: [Orgmode] %20 in file://... URL
[...] Please, do! :-) Giovanni Herein attached follows my patch. Please feel free for brickbats... Vincent. *** org.el.old Fri Nov 5 19:16:29 2010 --- org.el Sat Nov 13 05:50:54 2010 *** *** 9639,9647 opened in Emacs, unless an entry from org-file-apps that makes use of groups in a regexp matches. If the file does not exist, an error is thrown. ! (let* ((file (if (equal path ) buffer-file-name ! (substitute-in-file-name (expand-file-name path (file-apps (append org-file-apps (org-default-apps))) (apps (org-remove-if 'org-file-apps-entry-match-against-dlink-p file-apps)) --- 9639,9666 opened in Emacs, unless an entry from org-file-apps that makes use of groups in a regexp matches. If the file does not exist, an error is thrown. ! (let* ((%xx-decoded-path ! (let ((pos 0) (%xx-decoded-path path)) ! (setq %xx-decoded-path path) ! (while (setq pos (string-match %\\([0-9A-F]\\)\\([0-9A-F]\\) %xx-decoded-path pos)) ! (setq pos (1+ pos) ! %xx-decoded-path (replace-match ! (string (let ((code 0) digit) ! (dotimes (i 2) ! (setq ! digit (aref (match-string (1+ i) %xx-decoded-path) 0) ! code (+ (if (= digit ?9) ! (- digit ?0) ! (- digit 55)) ! (* 16 code code)) ! t t %xx-decoded-path))) ! ;; remove //localhost/ prefix if any ! (and (string-match \\`//localhost/ %xx-decoded-path) ! (setq %xx-decoded-path (substring %xx-decoded-path 12))) ! %xx-decoded-path)) ! (file (if (equal path ) buffer-file-name ! (substitute-in-file-name (expand-file-name %xx-decoded-path (file-apps (append org-file-apps (org-default-apps))) (apps (org-remove-if 'org-file-apps-entry-match-against-dlink-p file-apps)) 2010-11-13 Vincent Belaïche vincen...@users.sourceforge.net * org.el (org-open-file): Decode %XX escapes in URL with file type, so that applications other than browsers are not confused with the filename. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] %20 in file://... URL
From: vincent@hotmail.fr To: emacs-orgmode@gnu.org; giovanni.rido...@yahoo.it Subject: Re: [Orgmode] %20 in file://... URL Date: Sat, 13 Nov 2010 07:18:42 +0100 CC: vincent@hotmail.fr [...] Please, do! :-) Giovanni Herein attached follows my patch. Please feel free for brickbats... Vincent. BTW, I made the patch based on a GIT pull, so the org.el I used should be almost the latest one --- unless people have pushed new versions since the time when I made the pull. Vincent ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] %20 in file://... URL
Hello, Sorry to dwell on it: I am just wondering, is there any reason why %20 and suchlikes are not supported with the file: protocole ? I not, I can submit a patch to correct this and have the % constructs decoded. BR, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] %20 in file://... URL
From: giovanni.rido...@yahoo.it To: vincent@hotmail.fr Subject: Re: [Orgmode] %20 in file://... URL Date: Tue, 26 Oct 2010 17:39:55 +0200 CC: emacs-orgmode@gnu.org [...] *But*, Vincent, why do you use %3A when the colon : works? ?-/ The reason is quite simple, I wrote a package called w32utils.el which does several things useful for MSWindows users, among which converting path of marked files in Dired mode to various format, like URL for navigator, for LaTeX hyperref, for orgmode, and backslashed MSWindows path (that was the primary purpose), amongst other. This package also makes it easier to open bash shell buffers (using MSYS bash) under emacs in MSWindows, and also allows some easier update of the default-directory variable when you make CD to some path (like changing the driver letter, or using the MSYS fstab links). If you are interested in that I can put w32utils.el on my page and send you a link. This is still very experimental, and the manual is not uptodate. Well, this package makes a strict and complete conversion of paths to URL, and this is the reason for the %3A. cheers, Giovanni BR, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] %20 in file://... URL
Which Org mode version are you using? M-x org-version RET And can you give an example of a link that does not work as expected? Best, -- David Hello, Thanks for the feedback. Here is an example of failing link: [[file://localhost/c%3A/msys/1.0/temp/foo.html][link]] the file exists on my PC as c:\msys\1.0\temp\foo.html I am under MSWindows XP. M-x org-version = Org-mode version 7.01 This is more or less the latest version on emacs trunk. BR, Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] %20 in file://... URL
Hello, My Org mode version is not able to interprete any `%20' or suchlike escape codes in file://... URL, is that normal ? Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: does #+PROPERTY still exist ?
Hello all, Thanks for all the feedback. I am using Org-mode version 6.33x which is the latest on emacs CVS repository --- that may be outdated as emacs is using bazaar now. What is not working is 1. Auto-completion of `#+PROP' does not work 2. `C-c C-x p' does not work. Look at the following example: --8-coupez ici--début--8--- #+PROPERTY: toto_ALL 1 2 3 * test Then I type here `C-c C-x p' --8-coupez ici---fin---8--- 2.1 The completion at `Property:' prompt does not propose `toto' 2.2 The completion at `Value:' prompt does not propose 1 2 or 3 Hope that this clarifies the issue. Vincent. PS-1: Where can I get the latest org-mode ? PS-2: Sorry for my first email contained an error, setting properties before the 1st heading does not work. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] Re: does #+PROPERTY still exist ?
Thanks for the feedback, I'll download the latest. Yes, I just meant that *completion* does not work for property name, addition of property works fine. Vincent. To: nicholas.do...@hp.com From: nicholas.do...@hp.com Subject: Re: [Orgmode] Re: does #+PROPERTY still exist ? Date: Thu, 23 Sep 2010 00:34:19 -0400 CC: vincent@hotmail.fr; emacs-orgmode@gnu.org; Nick Dokos nicholas.do...@hp.com wrote: Vincent Belaïche vincent@hotmail.fr wrote: ... 2.2 The completion at `Value:' prompt does not propose 1 2 or 3 Yes. I don't know how difficult it would be to add these features. Actually, pressing TAB after the value prompt *does* produce the list of allowed values in the more-or-less current version I'm running: Org-mode version 7.01trans (release_7.01h.500.gbbac.dirty) Nick ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] does #+PROPERTY still exist ?
In the org manual node `(org) Property syntax' one can read the following: --8-coupez ici--début--8--- If you want to set properties that can be inherited by any entry in a file, use a line like #+PROPERTY: NDisks_ALL 1 2 3 4 --8-coupez ici---fin---8--- However this does not seem to work. What I did to get the same effect is place a property drawer before the first title, and then set #+OPTIONS: skip:t In order to disable export of this drawer (because I am exporting drawers in general). I would like to know whether this is a bug, and if yes I can provide a patch to the manual with work-around explained above. BR, Vincent. PS: #+PROPERTY does not work with completion `C-M-i' either ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] Re: Verbatim export
Thanks for the feedback.
BR,
Vincent.
To: vincent@hotmail.fr
Subject: Re: [Orgmode] Re: Verbatim export
From: be...@norang.ca
Date: Fri, 9 Jul 2010 09:13:09 -0400
CC: emacs-orgmode@gnu.org
Vincent Belaïche vincent@hotmail.fr writes:
[...]
#+begin_example
- this -
#+end_example
: - this one too
: - and that one -
Thank you for your quick reply, this is not exactly what I was looking
for. What you propose will encapsulate all the text into a
pre class=example /pre block. This means that the font and
background color are changed. I would not like this to happen, just the
characters to lose their special meaning.
Probably my initial email was confusing because I used the term
verbatim which in LaTeX changes the font. What I am looking for is to
make some text to be interpreted litterally, without having all the
surrounding formatters to be overloaded.
The dash is not a very good example because most of the time the
solution is just not to place any dash at the beginning of a line.
However I had the following issue: I wanted to quote some text (so using
#+begin/end_quote), and this text was beginning with a dash, then I
didn't know how to escape the dash.
The issue which I meet more often is when there are some `[0]' which I
don't want to be interpreted as footnotes, so I was proposing some
general solution like
\verbatim{EOF}In reference [0] EOF.
Another solution would be to have a \relax{} macro, then the following
would also work
In reference [\relax{}0]
\relax would also make it for like for dashes:
#+begin_quote
\relax{}- this dash is not a bullet mark
#+end_quote
Well, there are several ways to solve the issue. I am not sure which is
better.
The only other thing that works today that I'm aware of is you surround
your text with equal signs as in =[0]= but this also probably doesn't do
exactly what you want for both LaTeX and HTML export. This uses \texttt
in LaTeX and code.../code in HTML.
In HTML you're free to defined CSS for the code block but you won't
end up with a verbatim block in LaTeX. I proposed the two previous
examples because preceeding the text with ': ' creates
a \begin{verbatim} block in LaTeX.
If you document is targeted only for LaTeX export then you can use LaTeX
macros directly in the source.
Regards,
Bernt
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
_
Découvrez Microsoft Security Essentials, l'antivirus gratuit par Microsoft
http://clk.atdmt.com/FRM/go/212688364/direct/01/___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Verbatim export
Hello,
I would like to know how to make some sequence of characters to be
verbatim, ie that special characters lose their special meaning.
For instance in the following quote the first `-' will be interpreted as
a bullet point when exporting to HTML
#+begin_quote
- this -
#+end_quote
So I tried this:
#+begin_quote
~-~ this -
#+end_quote
but then the first `-' is not in the same font as the second one, it
looks exaclty the same as if I had used the code =xxx= font
specfication.
I also tried this:
#+begin_quote
\- this -
#+end_quote
I does not work (the first dash is not exported at all).
The same problem is for `[0]', how can you get this string not to be
interpreted as a footnote reference.
It should be possible to make the following type of things:
#+begin_verbatim
[0]
#+end_verbatim
or \verbatim{EOF}Hello - EOF
where EOF can be any string that is not found in the verbatim string. so
\verbatim{.}Hello - .
would to the same as \verbatim{xxx}Hello - xxx.
In the same vein, it would be useful to have some \relax{} macro not
expanding to anything, this way _\relax{} some underlining with
underlined leading spaces_ would work.
BR,
Vincent.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] Re: Verbatim export
[...]
#+begin_example
- this -
#+end_example
: - this one too
: - and that one -
Thank you for your quick reply, this is not exactly what I was looking
for. What you propose will encapsulate all the text into a
pre class=example /pre block. This means that the font and
background color are changed. I would not like this to happen, just the
characters to lose their special meaning.
Probably my initial email was confusing because I used the term
verbatim which in LaTeX changes the font. What I am looking for is to
make some text to be interpreted litterally, without having all the
surrounding formatters to be overloaded.
The dash is not a very good example because most of the time the
solution is just not to place any dash at the beginning of a line.
However I had the following issue: I wanted to quote some text (so using
#+begin/end_quote), and this text was beginning with a dash, then I
didn't know how to escape the dash.
The issue which I meet more often is when there are some `[0]' which I
don't want to be interpreted as footnotes, so I was proposing some
general solution like
\verbatim{EOF}In reference [0] EOF.
Another solution would be to have a \relax{} macro, then the following
would also work
In reference [\relax{}0]
\relax would also make it for like for dashes:
#+begin_quote
\relax{}- this dash is not a bullet mark
#+end_quote
Well, there are several ways to solve the issue. I am not sure which is
better.
Vincent
HTH,
Bernt
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
_
Découvrez Microsoft Security Essentials, l'antivirus gratuit par Microsoft
http://clk.atdmt.com/FRM/go/212688364/direct/01/___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] Poll: Who is using these commands
I use some of the navigation commands and C-c C-v (very often), but it would be quite fine to have other bindings provided that this is well advertised in the release note. I also often use C-c / way, for more refined queries. So go ahead! Vincent. Date: Sun, 9 May 2010 00:28:00 -0300 Subject: Re: [Orgmode] Poll: Who is using these commands From: daniel...@gmail.com To: carsten.domi...@gmail.com CC: emacs-orgmode@gnu.org Go ahead! I don't use them. Daniel 2010/5/8 Carsten Dominik carsten.domi...@gmail.com Hi everyone, I am wondering: How many of your are using these keys C-c C-f C-c C-b C-c C-n C-c C-p for navigation through the outline? These are first class keys, and I would have good uses for these keys if most people don't actually use them. Another question: C-c C-v currently make the TODO sparse tree. I would like to put this tree on `C-c / t' which would be quite logical and free up another first class key. Opinions, veto-attempts? Thanks! - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode _ Découvrez Windows Phone 7 : Une nouvelle ère de téléphones ! http://www.microsoft.com/windowsmobile/fr-fr/cmpn1/windowsphone7series/default.mspx___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Bulk] [Orgmode] Column width in export
Thanks Giovanni,
The documentation is however incomplete, the info node (org) Column
groups does not says that the `/' in the first field has the effect of
excluding the row from export. Actually when you read this info node,
what you (or better said I) understand is that the `/' indicates that
this special row is used to specify column grouping.
Therefore I propose the attached patch to documentation.
Vincent.
PS-1: Sorry if sometimes I disturbe this group with naive questions.
PS-2: This is a resend, it seems that the previous message was not
dispatched due to this that I made a too big attachement (tarzipped
complete manual old and new version in addition to patch).
Change log:
###
2010-04-16 Vincent Belaïche vincent@hotmail.fr
* org.texi (Column width and alignment): add information how to exclude
special row from export.
Patch:
###
*** org.texi.oldFri Apr 16 19:57:15 2010
--- org.texiFri Apr 16 20:07:59 2010
***
*** 1862,1867
--- 1862,1884
@samp{l} in a similar fashion. You may also combine alignment and field
width like this: @samp{l10}.
+ To exclude the special row containing the column width and/or alignment from
+ being exported, insert a dummy first column with @samp{/} in the field that
+ is on the special row, like this (considering the same example as previously):
+
+ @example
+ @group
+ |---+---+|
+ | / | | 6|
+ | # | 1 | one|
+ | # | 2 | two|
+ | # | 3 | This= |
+ | # | 4 | four |
+ |---+---+|
+ @end group
+ @end example
+
+
@node Column groups, Orgtbl mode, Column width and alignment, Tables
@section Column groups
@cindex grouping columns in tables
From: giovanni.rido...@yahoo.it
To: vincent@hotmail.fr
CC: emacs-orgmode@gnu.org
Subject: Re: [Bulk] [Orgmode] Column width in export
Date: Wed, 14 Apr 2010 13:26:31 +0200
Vincent Belaïche vincent@hotmail.fr writes:
| salut | dsdd |
| 30 | |
| gvrag f gfegegergrgh rghrghr ghrh =| gerg |
When exported to HTML there is one table row with `30' in it. Is there
anyway to make this row not exported as a row (but possibly exploited in
other ways) ?
In the manual, in the table section, subsection Column groups
it is written:
In order to specify column groups, you can use a special row where the
first field contains only `/'. The further fields can either contain
Before posting, please, read, or, at least, search, skim the manual
to find a possible solution.
Giovanni
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [PATCH] docstring bug
I think that
@samp{.}
should rather be replaced by
`.' or `'
than by (without simple quotes)
The `...@samp' marco is used for Texinfo source code, while simple quotes
(`') are to be used in docstring.
With my version of org, both `' and `.' work, but maybe the prefix (`.'
or `') should be some customizable string.
Vincent.
To: davi...@stats.ox.ac.uk
From: be...@norang.ca
Date: Fri, 16 Apr 2010 20:16:50 -0400
CC: emacs-orgmode@gnu.org
Subject: [Orgmode] Re: [PATCH] docstring bug
Dan Davison davi...@stats.ox.ac.uk writes:
In the docstring for org-structure-template-alist it says something that
I don't understand. I think perhaps it should be changed to
diff --git a/lisp/org.el b/lisp/org.el
index 1ef4395..ed602a5 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -9957,7 +9957,7 @@ This function can be used in a hook.
)
Structure completion elements.
This is a list of abbreviation keys and values. The value gets inserted
-it you type @samp{.} followed by the key and then the completion key,
+it you type followed by the key and then the completion key,
^^
if ?
usually `M-TAB'. %file will be replaced by a file name after prompting
for the file using completion.
There are two templates for each key, the first uses the original Org
syntax,
Dan
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
RE: [Orgmode] Filtering entries of a journal file with its datestamp
M-x occur with regexp ^\(\*\|Subject\s-+1\) gives 5 matches for ^\(\*\|Subject\s-+1\) in buffer: temp.org 1:* 2010-04-16 fri 2:Subject 1 4:Subject 1 7:* 2010-04-17 sat 10:Subject 1 Vincent. Date: Fri, 16 Apr 2010 05:28:26 + From: rbeni...@yahoo.es To: Emacs-orgmode@gnu.org CC: Subject: [Orgmode] Filtering entries of a journal file with its datestamp I have a simple journal .org file like this: --Begin file--- * 2010-04-16 fri Subject 1 Subject 2 Subject 1 Subject 40 * 2010-04-17 sat Subject 2 Subject 3 Subject 1 Subject 40 --End file-- Every subject is only one line. I would like to print the journal but including only the lines with a specific content, determined by a search, like the following -Buffer to print- * 2010-04-16 fri Subject 1 Subject 1 * 2010-04-17 sat Subject 1 -- --Another buffer to print- * 2010-04-16 fri Subject 40 * 2010-04-17 sat Subject 40 -- I have tried org-occur, but only marks the searched string; I also have tried occur but generate a list without the dates, and cannot be printed. I would appreciate any hint. Miguel Ruiz Sevilla, Spain. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode _ Consultez gratuitement vos emails Orange, Gmail, Free, ... directement dans HOTMAIL ! http://www.windowslive.fr/hotmail/agregation/___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Templates for drawer export
Hello all, Are there any way to make a template for drawer export, ie to define how the layout how a drawer would be exported to some format. Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Column width in export
Hello all, Here is an example Org document: ### * Example | salut | dsdd | | 30 | | | gvrag f gfegegergrgh rghrghr ghrh erh ghrhr hr htrhtr htrh trh trh trh trh | gerg | ** Next # When exported to HTML there is one table row with `30' in it. Is there anyway to make this row not exported as a row (but possibly exploited in other ways) ? Vincent. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Horizontal rule after list
Hello Dominik and al, I am new on this list, and also I am a new Org mode user. Here is an example of Org document: ### * Example 1. item 1 2. item 2 - * Next # When I export this to HTML the horizontal rule is included in the second list element, although its identation is not the same as the 2nd list element. I have found a work-around by inserting a page break character (`C-Q C-L') immediately before the horizontal rule, but I think that there is some issue. BR, Vincent. PS: Congratulations for Org, it's great! ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] HTML export of properties
Dear all, Just a question from an ignorant: I found that there is some way to export drawers with the `d:t' option, however, I could not find any such thing for properties export. Did I miss it ? Vincent. PS: It seems that I am not yet on the list, please include me in answer until my admission if any. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
