Re: [O] [PATCH] Reschedule "++" repeaters on same day if in future

Nicolas Goaziou writes: > Don March writes: >> If you have a task with the following timestamp: >> >> SCHEDULED: <2016-06-19 Sun 21:00 ++1w> >> >> then marking it as DONE at [2016-06-27 at 07:00] should [...] > ISYM [2016-06-26 at 07:00]. Yes :) Thanks for understanding anyway. (and ITYM

Re: [O] Blank lines in LaTeX output due to org-mode comments

> For me, using the "@@comment:..@@" syntax gives exactly the same > results as using "# ..." (an extra blank line in the output). Only if you write them on a line on their own. > Regardless of what the current org syntax is defined as, I am trying > to argue that it is counter-intuitive, and als

Re: [O] Blank lines in LaTeX output due to org-mode comments

On Thu, Jun 30, 2016 at 5:23 PM, Nicolas Goaziou wrote: > Mark Edgington writes: > >> I'm inclined to view it more as a bug, because it makes it impossible to >> place comments within a paragraph. > > This is per Org syntax. "# ..." is not meant as an inline paragraph. You > can comment inline wi

Re: [O] Blank lines in LaTeX output due to org-mode comments

Mark Edgington writes: > I'm inclined to view it more as a bug, because it makes it impossible to > place comments within a paragraph. This is per Org syntax. "# ..." is not meant as an inline paragraph. You can comment inline with something like @@comment:...@@. Regards,

Re: [O] Need to update documentation to reflect export block syntax

Kaushal Modi gmail.com> writes: > Mark The online documentation corresponds to the stable releases of org-mode only. > The master branch is the dev branch. The only way to access the latest documentation is via the Info manual (M-x info in emacs to access that is the best way IMO). Thanks, I s

Re: [O] Blank lines in LaTeX output due to org-mode comments

One other use case: when you want to comment out a single line in a paragraph, or have a few different lines within a paragraph that you wish to be able to select among by leaving only only one of them uncommented.

Re: [O] Blank lines in LaTeX output due to org-mode comments

Nicolas Goaziou nicolasgoaziou.fr> writes: > Mark Edgington gmail.com> writes: > > > Assume we have the following sample org-mode document: > > > > * Test Heading > > test test test test test test test > > test test test test test test test > > test test test test test test test > > # HERE IS A

Re: [O] Blank lines in LaTeX output due to org-mode comments

Hello, Mark Edgington writes: > Assume we have the following sample org-mode document: > > * Test Heading > test test test test test test test > test test test test test test test > test test test test test test test > # HERE IS A COMMENT > TEST TEST TEST TEST TEST TEST TEST > TEST TEST TEST TES

[O] Blank lines in LaTeX output due to org-mode comments

Assume we have the following sample org-mode document: * Test Heading test test test test test test test test test test test test test test test test test test test test test # HERE IS A COMMENT TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TES

[O] colored-links take 2

I forgot a little piece in the last patch. This one is probably right. It is based off of https://github.com/jkitchin/org-mode/blob/colored-link-3. diff --git a/lisp/org.el b/lisp/org.el index 89b72bc..451a668 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -1867,6 +1867,18 @@ return the description

Re: [O] patch for custom colored links in org-mode

I think I have attached the right patch that does this. Let me know what you think. Nicolas Goaziou writes: > Hello, > > John Kitchin writes: > >> I took a stab at this implementation here: >> >> https://github.com/jkitchin/org-mode/compare/master...colored-link-2?expand=1 > > Thank you. > > Co

Re: [O] scaling graphics in org-mode exported to latex

Alan Schmitt writes: > On 2016-06-30 14:42, Sharon Kimble writes: > >> I'm trying to get a 'list of figures' in an org-mode export to latex, >> but I'm finding difficulties in inserting graphics in org-mode. My >> graphic insert code is - >> >> #+CAPTION: Percutaneous endoscopic gastrostomy tube

Re: [O] scaling graphics in org-mode exported to latex

Max Linke writes: > I typically set a fixed width in latex like so. > > #+CAPTION: Percutaneous endoscopic gastrostomy tube > #+ATTR_LaTeX: :width 0.3\linewidth > > [[./images/percutaneous-endoscopic-gas.jpg]] > > Important to note that I write `:width` with a beginning double point. > I ca

Re: [O] Need to update documentation to reflect export block syntax

Mark Edgington writes: > It also might be worthwhile to have org-mode warn users (at least for a > number of new releases) who happen to be using the old format, explaining > that they need to use the new one to avoid problems when exporting. This already done in ORG-NEWS. Regards,

Re: [O] Need to update documentation to reflect export block syntax

@Mark The online documentation corresponds to the stable releases of org-mode only. The master branch is the dev branch. The only way to access the latest documentation is via the Info manual (M-x info in emacs to access that is the best way IMO). -- -- Kaushal Modi

Re: [O] Need to update documentation to reflect export block syntax

Hello, Mark Edgington writes: > I recently updated my org-mode git repository (for a long time I've > had an older git version that I was using), and I am now having > problems when doing latex exports. > > I bisected with git to find that the "problem" starts with this revision: > > commit 5431

Re: [O] Need to update documentation to reflect export block syntax

It also might be worthwhile to have org-mode warn users (at least for a number of new releases) who happen to be using the old format, explaining that they need to use the new one to avoid problems when exporting.

[O] Need to update documentation to reflect export block syntax

I recently updated my org-mode git repository (for a long time I've had an older git version that I was using), and I am now having problems when doing latex exports. I bisected with git to find that the "problem" starts with this revision: commit 54318add34f09ff39d3fd034a4c1a89f60fd8759 Author:

Re: [O] BUG: swapped utf-8 symbols in org-entities

Hello Nicolas, Attached is the patch, as requested. I'm not sure what were the conclusions of the side discussion, but I do want to point out that my change is in accordance with unicode symbol names and with the symbols that pdflatex prints on paper. Thanks and regards, Kosta -- Konstantin Kli

Re: [O] scaling graphics in org-mode exported to latex

Hello, Max Linke writes: > I typically set a fixed width in latex like so. > > #+CAPTION: Percutaneous endoscopic gastrostomy tube > #+ATTR_LaTeX: :width 0.3\linewidth > [[./images/percutaneous-endoscopic-gas.jpg]] > > Important to note that I write `:width` with a beginning double point.

Re: [O] scaling graphics in org-mode exported to latex

I typically set a fixed width in latex like so. #+CAPTION: Percutaneous endoscopic gastrostomy tube #+ATTR_LaTeX: :width 0.3\linewidth [[./images/percutaneous-endoscopic-gas.jpg]] Important to note that I write `:width` with a beginning double point. I can't get the `scale` to work even with

Re: [O] scaling graphics in org-mode exported to latex

On 2016-06-30 14:42, Sharon Kimble writes: > I'm trying to get a 'list of figures' in an org-mode export to latex, > but I'm finding difficulties in inserting graphics in org-mode. My > graphic insert code is - > > #+CAPTION: Percutaneous endoscopic gastrostomy tube > #+ATTR_LaTeX: scale=0.2 > [[

[O] scaling graphics in org-mode exported to latex

I'm trying to get a 'list of figures' in an org-mode export to latex, but I'm finding difficulties in inserting graphics in org-mode. My graphic insert code is - --8<---cut here---start->8--- #+CAPTION: Percutaneous endoscopic gastrostomy tube #+ATTR_LaTeX: sca

Re: [O] ox-clip.el

I’m quite confused with the difference between CLIPBOARD and PRIMARY in X11 and in OS X. Evil calls `x-select-text’ in `evil-visual-{pre,post}-command’. And here is the document of `x-select-text’: x-select-text is an alias for ‘gui-select-text’ in ‘select.el’. (x-select-text TEXT) This funct

Re: [O] [PATCH] Reschedule "++" repeaters on same day if in future

Hello, Don March writes: > If you have a task with the following timestamp: > > SCHEDULED: <2016-06-19 Sun 21:00 ++1w> > > then marking it as DONE at [2016-06-27 at 07:00] should (debatably) > result in ISYM [2016-06-26 at 07:00]. > SCHEDULED: <2016-06-26 Sun 21:00 ++1w> > > but instea

Re: [O] ox-clip.el

Thanks for the feedback. I noticed at the bottom of `gui-set-selection': Note that on MS-Windows, primary and secondary selections set by Emacs are not available to other programs. It looks like Emacs won't support this out of the box soon ;) > > But the text to be copied here is in RTF, but Emacs

Re: [O] patch for custom colored links in org-mode

Hello, John Kitchin writes: > I took a stab at this implementation here: > > https://github.com/jkitchin/org-mode/compare/master...colored-link-2?expand=1 Thank you. Could you send the patch on the ML instead? It is better for commenting and archiving. Also make sure to patch against master br

Re: [O] Why no secure code retrieval

Hello, Arun Isaac writes: >> However, gpg signing release tag commits is dead simple and would >> take a total of maybe 10 minutes of work over the lifetime of the project >> (please correct me if I'm wrong). > > I second this statement. GPG signing sounds good to me. We should do > this. GPG s

Re: [O] org-match-string-no-properties vs. match-string-[no-]properties

Hello, Michael Welle writes: > org-compat.el has this line: > > (define-obsolete-function-alias 'org-match-string-no-properties > 'match-string-properties "Org 9.0") > > Shouldn't it be match-string-no-properties? Good catch. Fixed. Thank you. Regards, -- Nicolas Goaziou