[O] fr: org-git-version to show branch name.

[Samuel Wales]

fr: org-git-version to show branch name.

-- 
The Kafka Pandemic: 

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
.

Re: [O] refile too slow

[Samuel Wales]

On 10/5/17, Nicolas Goaziou  wrote:
>> i think delete-dups is suspicious here.  is its only purpose to
>
> Why is delete-dups suspicious? Have you got a very large number of
> refile locations? If so, would it make sense to refine your target
> definitions?

already do that.  my fallback "get most things down to a reasonable
level" refile and refile goto were ok until recently.  then they
became untenably slow.  i can't refine it more without missing stuff
that i need.

> Its purpose, as its name suggests, is to remove duplicate refile
> locations you could get.

so only useful if i set the variable with duplicate stuff?

===

delete-dups seems suspicious but what do i know.  i wonder if
cl-delete-duplicates is more efficient.

(defun delete-dups (list)
  "Destructively remove `equal' duplicates from LIST.
Store the result in LIST and return it.  LIST must be a proper list.
Of several `equal' occurrences of an element in LIST, the first
one is kept."
  (let ((tail list))
(while tail
  (setcdr tail (delete (car tail) (cdr tail)))
  (setq tail (cdr tail
  list)

Re: [O] Nested smart quotes

[Martin Alsinet]

On Thu, Oct 5, 2017 at 4:58 PM Adonay Felipe Nogueira 
wrote:

> What about using org-entities for these quotes?
>
> \ldquo{}Hello \lsquo{}World\rsquo{}!\rdquo{}
>
> This is Org mode syntax, not LaTeX.
>
>
Adonay:

I wanted to solve this using smart quotes, that is when I write I don't
have to worry with anything other than writing, and the light formatting of
org-mode is great for that (* for emphasis, / for italics, etc.) While the
solution you are proposing is technically correct, it achieves the result,
I find it too verbose and distracting from the text.

Actually I solved the problem by upgrading to org-mode 9.1.2 and leaving a
space between the inner quote and the enclosing double quote.

Thanks and regards


Martín

Re: [O] Nested smart quotes

[Adonay Felipe Nogueira]

What about using org-entities for these quotes?

\ldquo{}Hello \lsquo{}World\rsquo{}!\rdquo{}

This is Org mode syntax, not LaTeX.

Martin Alsinet  writes:

> Hello!
>
> My name is Martin and I use org-mode every day. This is my first message to
> the mailing list, and I wanted to ask if somebody could help me with a
> problem I encountered when exporting a document with nested smart quotes.
>
> I have submitted the same question to the emacs Stack Exchange, and someone
> suggested there to send a message to this list. I assume many people here
> reads their email inside emacs, and since this email has embedded images, you
> might see it better formatted in SO.
>
> I have found that the smart-quotes option of org-mode does not export
> properly the quotes when they are nested (single quotes inside double
> quotes), but only when they coincide at the start or the end of the quote.
>
> Maybe the problem will be clearer with an example:
>
> #+TITLE: Smart quotes example
> #+OPTIONS: toc:nil ':t
> #+LANGUAGE: en
> #+LATEX_CLASS: book
> She said to me: "Rick screamed, 'let's go together'" 
>
> This gets exported to TeX as:
>
> She said to me: ``Rick screamed, `let's go together'''
>
> Which gets rendered as PDF as:
>
> The order of the closing quotes is wrong
>
> The order of the closing quotes gets reversed, it first closes the outside
> double quotes and then the nested single quote.
>
> I have tried leaving a space between them, but that is arguably worse
>
> Org:
>
> She said to me: "Rick screamed, 'let's go together' " 
>
> TeX:
>
> She said to me: ``Rick screamed, `let's go together' "
>
> PDF:
>
> Internal quotes are ok, closing double quote is wrong
>
> In this case, the internal single quotes are rendered correctly, but the
> closing quote is not converted into its "smart" version.
>
> If the nested quotes are in such a way that there are other characters
> between the quotes, that is they are not together at the start or the end of
> the quote, they get rendered correctly.
>
> Thanks in advance
>
> Martin
>
>

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
  gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.

Re: [O] Nested smart quotes

[Colin Baxter]

> Nick Dokos  writes:

> Martin Alsinet  writes:
>> ...  I have found that the smart-quotes option of org-mode does
>> not export properly the quotes when they are nested (single
>> quotes inside double quotes), but only when they coincide at the
>> start or the end of the quote.
>> 
>> Maybe the problem will be clearer with an example:
>> 
>> #+TITLE: Smart quotes example #+OPTIONS: toc:nil ':t #+LANGUAGE:
>> en #+LATEX_CLASS: book She said to me: "Rick screamed, 'let's go
>> together'"
>> 

> This example has the additional problem of the apostrophe in
> "let's", which basically causes more mayhem. Let's simplify the
> example a bit by considering


> Going back to the original string with the apostrophe, I don't see
> any way that org or TeX can deal with it except by really
> understanding what is being said: having the apostrophe be denoted
> by the same symbol as the closing quote is bound to introduce
> ambiguities. In these days of Unicode, I think the only solution
> is to use xelatex or another Unicode-cognizant TeX system and to
> use a proper apostrophe.

> -- Nick


TeX/LaTeX were after all designed primarily for mathematics. That said,
it might be worth looking at the upquote package:

https://ctan.org/pkg/upquote.

-- 
Colin Baxter
m43...@yandex.com
-
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
-
"There is no more common error than to assume that, because prolonged and
accurate mathematical calculations have been made, the application of
the result to some fact of nature is absolutely certain." A. N. Whitehead

Re: [O] Nested smart quotes [fixed]

[Martin Alsinet]

On Thu, Oct 5, 2017 at 2:41 PM Martin Alsinet  wrote:

> Hello Nick. First, thank you so much for your detailed answer.
>
> I'm not sure whether smart quotes can be made smarter, perhaps by
>> detecting the problem and inserting the small space \, to resolve the
>> ambiguity; but the manual space solution should have worked: what
>> version of org are you using?
>>
>> FWIW, mine is latest master: Org mode version 9.1.2
>> (release_9.1.2-84-geeaf9a @ /home/nick/src/emacs/org/org-mode/lisp/)
>>
>
> I am using Org mode version 8.2.10, I will update my version and try again.
>
>
I updated Org-mode to the last version (9.1.2) from the orgmode.org ELPA
sources and the problem went away.

Separating the nested quotes with a space does the trick:

She said to me: "Rick screamed, 'let's go together' "

Now the closing quote gets "smarted" in the exported PDF file.

Thank you very much


Martin

Re: [O] Nested smart quotes

[Martin Alsinet]

Hello Nick. First, thank you so much for your detailed answer.

On Thu, Oct 5, 2017 at 2:16 PM Nick Dokos  wrote:

>
> This example has the additional problem of the apostrophe in "let's", which
> basically causes more mayhem. Let's simplify the example a bit by
> considering
>
> She said to me: "Rick screamed, 'let us go together'"
>
> which when export to TeX becomes:
>
> She said to me: ``Rick screamed, `let us go together'''
>
> and TeX misinterprets the three closing single quotes as (closing
> double quote, closing single quote) instead of (closing single quote,
> closing double quote).
>
>
I was beginning to suspect that, I didn't see it at first, but after
writing and explaining the problem, it dawned on me that it could be LaTeX
that cannot correctly parse the three consecutive single quotes.


> >
> > Internal
> >
> > In this case, the internal single quotes are rendered correctly, but the
> closing quote is not converted into its "smart" version.
> >
> > If the nested quotes are in such a way that there are other characters
> between the quotes, that is they are not together at the start or the end
> of the quote, they get rendered correctly.
>
> I'm not sure whether smart quotes can be made smarter, perhaps by
> detecting the problem and inserting the small space \, to resolve the
> ambiguity; but the manual space solution should have worked: what
> version of org are you using?
>
> FWIW, mine is latest master: Org mode version 9.1.2
> (release_9.1.2-84-geeaf9a @ /home/nick/src/emacs/org/org-mode/lisp/)
>

I am using Org mode version 8.2.10, I will update my version and try again.


Martin

Re: [O] Nested smart quotes

[Colin Baxter]

> Martin Alsinet  writes:


> #+TITLE: Smart quotes example #+OPTIONS: toc:nil ':t #+LANGUAGE:
> en #+LATEX_CLASS: book She said to me: "Rick screamed, 'let's go
> together'"

> This gets exported to TeX as:

> She said to me: ``Rick screamed, `let's go together'''

> Which gets rendered as PDF as:

> The order of the closing quotes is wrong

> The order of the closing quotes gets reversed, it first closes the
> outside double quotes and then the nested single quote.

> I have tried leaving a space between them, but that is arguably
> worse

> Org:

> She said to me: "Rick screamed, 'let's go together' "

> TeX:

> She said to me: ``Rick screamed, `let's go together' "

> PDF:

> Internal quotes are ok, closing double quote is wrong

> In this case, the internal single quotes are rendered correctly,
> but the closing quote is not converted into its "smart" version.

> If the nested quotes are in such a way that there are other
> characters between the quotes, that is they are not together at
> the start or the end of the quote, they get rendered correctly.

> Thanks in advance

> Martin

What about

She said to me: \lq\lq Rick screamed, \lq let's go together\rq\nbsp{}\rq\rq


-- 
Colin Baxter
m43...@yandex.com

Re: [O] Nested smart quotes

[Nick Dokos]

Martin Alsinet  writes:

> ...
> I have found that the smart-quotes option of org-mode does not export 
> properly the quotes when they are nested (single quotes inside double 
> quotes), but only when they coincide at the
> start or the end of the quote.
>
> Maybe the problem will be clearer with an example:
>
> #+TITLE: Smart quotes example
> #+OPTIONS: toc:nil ':t
> #+LANGUAGE: en
> #+LATEX_CLASS: book
> She said to me: "Rick screamed, 'let's go together'" 
>

This example has the additional problem of the apostrophe in "let's", which
basically causes more mayhem. Let's simplify the example a bit by considering

She said to me: "Rick screamed, 'let us go together'"

which when export to TeX becomes:

She said to me: ``Rick screamed, `let us go together'''

and TeX misinterprets the three closing single quotes as (closing
double quote, closing single quote) instead of (closing single quote,
closing double quote).

Modifying the TeX output to this:

She said to me: ``Rick screamed, `let us go together'\,''

makes TeX interpret things correctly and it is also visually pleasant
(IMO of course).

> This gets exported to TeX as:
>
> She said to me: ``Rick screamed, `let's go together'''
>
> Which gets rendered as PDF as:
>
> The orde
>
> The order of the closing quotes gets reversed, it first closes the outside 
> double quotes and then the nested single quote.
>
> I have tried leaving a space between them, but that is arguably worse
>
> Org:
>
> She said to me: "Rick screamed, 'let's go together' " 
>
> TeX:
>
> She said to me: ``Rick screamed, `let's go together' "

I do not get this with the space. I get this in the TeX output:

   She said to me: ``Rick screamed, `let us go together' ''

which has a larger space between the single and the double quote at the end
than with \, but is otherwise OK.


>
> Internal
>
> In this case, the internal single quotes are rendered correctly, but the 
> closing quote is not converted into its "smart" version.
>
> If the nested quotes are in such a way that there are other characters 
> between the quotes, that is they are not together at the start or the end of 
> the quote, they get rendered correctly.

I'm not sure whether smart quotes can be made smarter, perhaps by
detecting the problem and inserting the small space \, to resolve the
ambiguity; but the manual space solution should have worked: what
version of org are you using?

FWIW, mine is latest master: Org mode version 9.1.2
(release_9.1.2-84-geeaf9a @ /home/nick/src/emacs/org/org-mode/lisp/)

Going back to the original string with the apostrophe, I don't see any
way that org or TeX can deal with it except by really understanding
what is being said: having the apostrophe be denoted by the same
symbol as the closing quote is bound to introduce ambiguities. In
these days of Unicode, I think the only solution is to use xelatex or
another Unicode-cognizant TeX system and to use a proper apostrophe.

-- 
Nick

Re: [O] Nested smart quotes

[Nicolas Goaziou]

Hello,

Martin Alsinet  writes:

> Maybe the problem will be clearer with an example:
>
> #+TITLE: Smart quotes example
> #+OPTIONS: toc:nil ':t
>
> #+LANGUAGE: en
> #+LATEX_CLASS: book
>
> She said to me: "Rick screamed, 'let's go together'"
>
> This gets exported to TeX as:
>
> She said to me: ``Rick screamed, `let's go together'''

This looks correct to me. For example, with french quotes, I get

  She said to me: \og Rick screamed, \og let's go together\fg{}\fg{}

which looks fine. Maybe LaTeX cannot handle this properly.


Regards,

-- 
Nicolas Goaziou

Re: [O] Release 9.1.2

[Cook, Malcolm]

> "Cook, Malcolm"  writes:
 > 
 > > Should we expect to find release notes at
 > > http://orgmode.org/Changes.html or somewhere else?
 > 
 > Yes, that's the place for human readable changelogs, which we update
 > for major and minor releases, not for bugfix releases.

Ah!  Understood.  Thanks!

> And http://orgmode.org/cgit.cgi/org-mode.git/log/ gives the detailed
 > git logs.
 > 
 > HTH,

It does!

> --
 >  Bastien

Re: [O] Release 9.1.2

[Bastien Guerry]

Hi,

"Cook, Malcolm"  writes:

> Should we expect to find release notes at
> http://orgmode.org/Changes.html or somewhere else?

Yes, that's the place for human readable changelogs, which we update
for major and minor releases, not for bugfix releases.

And http://orgmode.org/cgit.cgi/org-mode.git/log/ gives the detailed
git logs.

HTH,

-- 
 Bastien

Re: [O] Nested smart quotes

[Martin Alsinet]

Colin:

The beauty of smart quotes is that I don't have to see the ugly LaTeX
formatting in my org file, but the final document has the corresponding
opening and closing quote characters. While I do sprinkle some LaTeX here
and there in my org files, I think that would be going a little too far for
my taste.

Thanks anyway!

Martin


On Thu, Oct 5, 2017 at 12:22 PM Colin Baxter  wrote:

> > Martin Alsinet  writes:
>
>
> > #+TITLE: Smart quotes example #+OPTIONS: toc:nil ':t #+LANGUAGE:
> > en #+LATEX_CLASS: book She said to me: "Rick screamed, 'let's go
> > together'"
>
> > This gets exported to TeX as:
>
> > She said to me: ``Rick screamed, `let's go together'''
>
> > Which gets rendered as PDF as:
>
> > The order of the closing quotes is wrong
>
> > The order of the closing quotes gets reversed, it first closes the
> > outside double quotes and then the nested single quote.
>
> > I have tried leaving a space between them, but that is arguably
> > worse
>
> > Org:
>
> > She said to me: "Rick screamed, 'let's go together' "
>
> > TeX:
>
> > She said to me: ``Rick screamed, `let's go together' "
>
> > PDF:
>
> > Internal quotes are ok, closing double quote is wrong
>
> > In this case, the internal single quotes are rendered correctly,
> > but the closing quote is not converted into its "smart" version.
>
> > If the nested quotes are in such a way that there are other
> > characters between the quotes, that is they are not together at
> > the start or the end of the quote, they get rendered correctly.
>
> > Thanks in advance
>
> > Martin
>
> What about
>
> She said to me: \lq\lq Rick screamed, \lq let's go together\rq\nbsp{}\rq\rq
>
>
> --
> Colin Baxter
> m43...@yandex.com
>

Re: [O] Release 9.1.2

[Cook, Malcolm]

> Hi all,

Yay!  Thanks for org!  Always a game changer.  

Should we expect to find release notes at http://orgmode.org/Changes.html or 
somewhere else?

 > 
 > Org 9.1.2 is out.
 > 
 > Enjoy!
> 
 > --
 >  Bastien
 > 

[O] Nested smart quotes

[Martin Alsinet]

Hello!

My name is Martin and I use org-mode every day. This is my first message to
the mailing list, and I wanted to ask if somebody could help me with a
problem I encountered when exporting a document with nested smart quotes.

I have submitted the same question

to the emacs Stack Exchange, and someone suggested there to send a message
to this list. I assume many people here reads their email inside emacs, and
since this email has embedded images, you might see it better formatted in
SO.

I have found that the smart-quotes option of org-mode does not export
properly the quotes when they are nested (single quotes inside double
quotes), but only when they coincide at the start or the end of the quote.

Maybe the problem will be clearer with an example:

#+TITLE: Smart quotes example
#+OPTIONS: toc:nil ':t
#+LANGUAGE: en
#+LATEX_CLASS: book
She said to me: "Rick screamed, 'let's go together'"

This gets exported to TeX as:

She said to me: ``Rick screamed, `let's go together'''

Which gets rendered as PDF as:

[image: The order of the closing quotes is wrong]


The order of the closing quotes gets reversed, it first closes the outside
double quotes and then the nested single quote.

I have tried leaving a space between them, but that is arguably worse

Org:

She said to me: "Rick screamed, 'let's go together' "

TeX:

She said to me: ``Rick screamed, `let's go together' "

PDF:

[image: Internal quotes are ok, closing double quote is wrong]


In this case, the internal single quotes are rendered correctly, but the
closing quote is not converted into its "smart" version.

If the nested quotes are in such a way that there are other characters
between the quotes, that is they are not together at the start or the end
of the quote, they get rendered correctly.

Thanks in advance


Martin

Re: [O] Trying to get chart from table working

[Peter Davis]

On Thu, Oct 5, 2017, at 10:39 AM, Nicolas Goaziou wrote:
> Hello,
> 
> Peter Davis  writes:
> 
> > On Wed, Oct 4, 2017, at 01:36 AM, Eric S Fraga wrote:
> >> On Tuesday,  3 Oct 2017 at 15:28, Peter Davis wrote:
> >> > Yup. I deleted the source block and the results line, and now export to
> >> > HTML and PDF works with no problems.
> >> 
> >> Please post the complete file (t.org?) to this list.
> >
> > Ok. The original (t.org) is exactly what you posted a few days ago. This
> > fails to export HTML. ("Wrong type argument")
> 
> As another data point, I cannot reproduce the error with "t.org".

Thanks. It seems I have two problems:

1) Something in my emacs/org setup is causing this to fail outright,
with a "wrong type parameter" error. If I run in a shell window with no
init files, I don't get that error.

2) Something is preventing gnuplot from working. Even when I can
successfully export to HTML or PDF, I don't get any graph.

Thanks,
-pd

-- 
  Peter Davis
  www.techcurmudgeon.com

Re: [O] [ANN] Agenda speed up

[Kyle Meyer]

Nicolas Goaziou  writes:

> Kyle Meyer  writes:
>
>> Nicolas Goaziou  writes:
>>
>>> If there is no more feedback nor objection, I'll merge the branch in
>>> master before the end of the week.
>>
>> One issue I noticed: The sorting of categories defined in
>> org-agenda-sorting-strategy is not honored.  The default category
>> sorting for the agenda is to order the categories as they appear in the
>> agenda files.

[...]

> Fixed. Thank you.

Thank you.  Hit a second issue today.

(setq org-agenda-custom-commands
  '(("u" "Unschedule TODO entries" alltodo ""
 ((org-agenda-skip-function
   (lambda ()
 (org-agenda-skip-entry-if 'scheduled 'deadline)))
  (org-agenda-overriding-header "Unscheduled TODO entries: ")

On master and with an agenda file that contains

* TODO not scheduled

* TODO scheduled
SCHEDULED: <2017-10-07 Sat>

running "M-x org-agenda u" shows the "not scheduled" heading only.
wip-agenda-speedup show both entries.

-- 
Kyle

Re: [O] function for inserting a block

[Nicolas Goaziou]

Hello,

Eric Abrahamsen  writes:

> Nicolas Goaziou  writes:
>
>
> [...]
>
>> C-c C-x t is free, tho.
>
> Oops, I think that's what I meant to type. Here's the latest version of
> the patch -- I removed the bit fooling with the location of point at the
> end, as it seemed simpler was better. How's this look?

`newline-and-indent' and `mark' shouldn't be used in the function.

Otherwise, it looks good. Could you provide some tests for that in
"test-org.el"?

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: [O] refile too slow

[Nicolas Goaziou]

Hello,

Samuel Wales  writes:

> recent maint, but been a problem for a few mo.
>
> refile hits a wall.  depends on number of headers.
>
> i think delete-dups is suspicious here.  is its only purpose to
> eliminate the existing
> header?

Why is delete-dups suspicious? Have you got a very large number of
refile locations? If so, would it make sense to refine your target
definitions?

Its purpose, as its name suggests, is to remove duplicate refile
locations you could get.

Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: org-capture-templates with %^t

[Matt Lundin]

Matt Lundin  writes:

> After commit 51b431d01365211d4c40b07729d5d11d82b9dfe2,
> org-capture-templates containing %^t do not work as expected.
>
> The relevant capture template snippet looks like this:
>
> (setq org-capture-templates
>   '(("a" "Appointment" entry (file "~/inbox.org") "* %^{Appt}\n %^t%?\n 
> %U\n
> %a\n\n %i")))
>
> With this capture template, I am prompted to enter a time via
> org-read-date. The expected behavior is as follows:
>
>  - if I enter a date and time of day, the resulting timestamp should 
>contain the time of day:
>  - i.e., entering "Thu 8am" should yield "<2017-10-05 Thu 08:00>"
>
> What happens now:
>
>  - when I enter a date with a time of day, the timestamp is truncated
>and contains only a date
>  - I.e., entering "Thu 8am" now yields "<2017-10-05 Thu>"
>

There is a further bug here. With the capture template above, if I enter
a time range - i.e., an end time - the timestamp in the capture buffer
is incorrect.

Entering... "Thu 8am-10am" yields...

 <2017-10-05 Thu-10:00>

Best,
Matt

Re: [O] [PATCH] org-clock: Fix clock report sometimes ignoring hours before :wstart

[Nicolas Goaziou]

Hello,

Georgiy Tugai  writes:

> * lisp/org-clock (org-clocktable-steps): Fix weekly-step clock report
>   ignoring hours between start of period and start of week, when start
>   of period is on a day of week numerically less than start of week.
>
>   Clock report now always inserts a "week" starting at the start of
>   the period, if necessary; all following weeks start on the start of
>   the week as expected.

Thank you.

Would you mind adding a test in test-org-clock.el?

Regards,

-- 
Nicolas Goaziou

Re: [O] Trying to get chart from table working

[Nicolas Goaziou]

Hello,

Peter Davis  writes:

> On Wed, Oct 4, 2017, at 01:36 AM, Eric S Fraga wrote:
>> On Tuesday,  3 Oct 2017 at 15:28, Peter Davis wrote:
>> > Yup. I deleted the source block and the results line, and now export to
>> > HTML and PDF works with no problems.
>> 
>> Please post the complete file (t.org?) to this list.
>
> Ok. The original (t.org) is exactly what you posted a few days ago. This
> fails to export HTML. ("Wrong type argument")

As another data point, I cannot reproduce the error with "t.org".

Regards,

-- 
Nicolas Goaziou

[O] Naming a clocktable

[Shawn Way]

Is it possible to name a clocktable ala

#+NAME: tab:clock

to allow the output to be further processed by a source code block?


For example I would like to process the following results using a source block 
containing a perl script:

#+BEGIN: clocktable :maxlevel 4 :scope agenda :block today-2 :step day :link t 
:tags "-NONWORK" :properties ("ECO" "ALLTAGS")
  
  Daily report: [2017-10-03 Tue]
  | File |   ECO | ALLTAGS  | Headline  
   | Time   |  |  |  |
  
|--+---+--+--++--+--+--|
  |  |   ALL |  | *Total time*  
   | *7:56* |  |  |  |
  
|--+---+--+--++--+--+--|
  | Standard-Development.org |   |  | *File time*   
   | *0:00* |  |  |  |
  
|--+---+--+--++--+--+--|
  | Shawn.org|   |  | *File time*   
   | *7:56* |  |  |  |
  |  |   |  | 
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Non-Job%20Tasks][Non-Job 
Tasks]]| 1:32   |  |  |  |
  |  |   |  | \_  
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Adminstrative%20(E30)][Adminstrative
 (E30)]]  || 1:19 |  |  |
  |  |   |  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Walk%20Up%20Questions][Walk Up 
Questions]]  ||  | 0:25 |  |
  |  |   | :walkup: | \_  
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Walk%20Up%20Question%20from%20Chris%20Sasser%20at%20%5B2017-10-03%20Tue%2011:07%5D][Walk
 Up Question from Chris Sasser at...]] ||  |  | 0:25 |
  |  |   |  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Updating%20Org%20File][Updating 
Org File]]  ||  | 0:10 |  |
  |  |   |  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::TimeCards][TimeCards]]  
||  | 0:13 |  |
  |  |   |  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Balanced%20Score%20Card%20Meeting][Balanced
 Score Card Meeting]]||  | 0:31 |  |
  |  |   |  | \_  
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Email%20(E30)][Email (E30)]]
  || 0:04 |  |  |
  |  |   |  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Email%20Review][Email Review]]  
 ||  | 0:04 |  |
  |  |   |  | \_  
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Software%20Updates%20/%20Installation%20(E30)][Software
 Updates / Installation (E30)]]|| 0:09 |  |  |
  |  |   |  | 
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Jobs][Jobs]]
 | 5:38   |  |  |  |
  |  |   |  | \_  
[[file:c:/Users/sway/Engineering-Log/Shawn.org::9677%20(WO%2071728)][9677 (WO 
71728)]]  || 3:50 |  |  |
  |  |   | :walkup: | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Walk%20Up%20Question%20from%20Han%20at%20%5B2017-10-03%20Tue%2013:22%5D][Walk
 Up Question from Han at...]]||  | 0:07 |  |
  |  |   | :email:  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Email%20to%20Thad,%20Han%20at%20%5B2017-10-03%20Tue%2008:31%5D][Email
 to Thad, Han at {2017-10-03 Tue...]]   ||  | 0:02 |  |
  |  |   |  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Ship%20Loose%20Kit][Ship Loose 
Kit]] ||  | 0:48 |  |
  |  | 51071 |  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Update%20VLV%20BOM][Update VLV 
BOM]] ||  | 0:14 |  |
  |  |   |  | \_
[[file:c:/Users/sway/Engineering-Log/Shawn.org::Brine%20Tank][Brine Tank]]  
   ||  | 2:39 |  |
  |  |   |  | 

[O] Fontification for the inner bloc of two nested bloc

[Pierre-André Cornillon]

Dear org-mode users/gurus


I have a question about fontification of inner src bloc. I have already
submitted this question to the list a few days ago but it did not appear
(and I suspect my mail account to be blacklisted) So I apologize first if
this question is submitted another time to the list...

I have two nested blocks: one special (outer bloc) and one src (inner
bloc) like this
#+begin_bloc20171001122500
#+begin_src R :results value :session :exports both
  blip <- runif(2)
  test <- rnorm(2)
#+end_src
#+end_bloc20171001122500
and I want to have the native fontification property for the inner one.

I have already (setq org-src-fontify-natively t) in my .emacs and it
works like a charm for src blocks alone (not nested) but for nested
ones it breaks.

Is nested blocks are allowed and if so, is that possible to have that
fontification property ?

Thanks,
Pierre-Andre

Re: [O] Confused about the explanation for 'org-cycle'

[Alain . Cochard]

Nicolas Goaziou writes on Thu 28 Sep 2017 23:30:

 > There are already many ways in Emacs to find a variable. I'm not
 > convinced that adding such an appendix would be worth the trouble
 > creating and maintaining it.

 > As another data point, Emacs' manual doesn't contain an exhaustive
 > variable section either.

Fair enough.  So lack of such an appendix was not a good example of
excess of conciseness of the manual.

Thanks (to you and others) for the tips on how to get variables'
documentation.  I indeed should get used to these other methods.


-- 
EOST (École et Observatoire des Sciences de la Terre) 
IPG (Institut de Physique du Globe) | alain.coch...@unistra.fr
5 rue René Descartes   [bureau 106] | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France| Fax:   +33 (0)3 68 85 01 25