#+OPTIONS: latex:t toc:nil H:3
Hi Nicolas,
I've tried the example block but it doesn't export well.
[[file:/home/amos/Pictures/Screenshots/img-2017-09-29-100634.png]]
> - include this in a fixed-width area,
Um, do you mean putting a <10> at the top of the second column? I tried that
but it
It looks something like this: https://pastebin.com/bBFwPuwb
This is generated by
$ #+BEGIN: clocktable :maxlevel 0 :scope agenda :step day :tstart "<-1w>"
:tend "" :compact t
I am using Spacemacs. Are org-plus-contrib-20170918 &
evil-org-20170917.1447 the relevant packages?
On Tue, Sep 26,
alain.coch...@unistra.fr writes:
> I have a fresh example in mind to illustrate my point: this afternoon,
> I was looking for org-blank-before-new-entry. I vaguely remembered it
> existed and was searching the manual (from Info) with the regexps
> 'blank' and 'list'. Had the variable been
Hi Alain,
> I have a fresh example in mind to illustrate my point: this afternoon,
> I was looking for org-blank-before-new-entry. I vaguely remembered it
> existed and was searching the manual (from Info) with the regexps
> 'blank' and 'list'. Had the variable been mentioned, I would have
>
Thanks for your answer.
Nicolas Goaziou writes on Thu 28 Sep 2017 16:31:
> > More generally, I cannot remember the number of times when I read
> > the manual, do not understand it,
>
> This is exactly where the manual fails. What is the point of an
> exhaustive, yet not understandable,
Hello,
alan.wehm...@gmail.com writes:
> I have noticed that if I remove a hline in a org table used as a
> spreadsheet, the formulae for rows below where the hline was, change
> in a manner that makes them refer to the wrong row.
>
> Since hlines are not counted as rows in the spreadsheet,
On Thu, Sep 28, 2017 at 3:19 PM Nicolas Goaziou
wrote:
> I already answered to this problem. Use \star instead of *. It seems
> sub-optimal to prevent any emphasis markup because of a single
> problematic character.
>
OK.
> I mean this variable doesn't solve any
Kaushal Modi writes:
> On Thu, Sep 28, 2017 at 2:47 PM Nicolas Goaziou
> wrote:
>
>> Besides the fact that it is not available, is there any incentive to do
>> so?
>
>
> While talking to Amos (now CC'ed on this email) off-list on Gitter chat
>
On Thu, Sep 28, 2017 at 2:47 PM Nicolas Goaziou
wrote:
> Besides the fact that it is not available, is there any incentive to do
> so?
While talking to Amos (now CC'ed on this email) off-list on Gitter chat
regarding the ox-hugo package, he had this test case[1] where
Hello,
Amos Bird writes:
> How can I disable fontifications when exporting this:
>
> QueryID SQL Text Query Time (Seconds) Query Time Hot (Seconds)
> Q0 SELECT avg(c1) from (select Year, Month, count(*) as c1 from ontime
> group by Year, Month); 1.27 0.13
Hello,
Kaushal Modi writes:
> I see that many export options like org-export-with-emphasize,
> org-export-with-sub-superscripts cannot be set on per-subtree basis using
> properties.
[...]
> I believe that can be fixed by doing:
>
> (:with-emphasize
On Thu, Sep 28, 2017 at 1:28 PM Kaushal Modi wrote:
> .. and so on, and then one can have
>
> :EXPORT_WITH_EMPHASIZE: t
>
> or
>
> :EXPORT_WITH_EMPHASIZE:
>
> in the subtree property.
>
> Is there a reason why this support wasn't added in the first place?
> (Or does a
Hello,
I see that many export options like org-export-with-emphasize,
org-export-with-sub-superscripts cannot be set on per-subtree basis using
properties.
In ox.el, I see:
(defconst org-export-options-alist
'((:title "TITLE" nil nil parse)
(:date "DATE" nil nil parse)
(:author
On Thursday, 28 Sep 2017 at 12:10, Kyle Meyer wrote:
> I don't think maintaining a list of all Org's user options or commands
> is a good idea. It is better to point users to commands like
> apropos-user-option and apropos-command.
Or even "C-h f org- TAB" or "C-h v org- TAB" to see all org
Robert Horn writes:
> Nicolas Goaziou writes:
>
>> Completeness is not possible. For example, we do not document every
>> variable in the manual. Besides, when reading a pile of special rules
>> for special cases, the reader may lose focus and miss the whole concept.
>>
>>
Nicolas Goaziou writes:
> Completeness is not possible. For example, we do not document every
> variable in the manual. Besides, when reading a pile of special rules
> for special cases, the reader may lose focus and miss the whole concept.
>
> BTW, a "docstring" is the documentation you get
Hello,
alain.coch...@unistra.fr writes:
> As for the wording, I have nothing ecstatic to propose, but -- as a
> beginner and trying to think like one who is reading the manual for
> the first time while experimenting -- I would have been happy with
> something like:
>
>You can run global
Hello,
alain.coch...@unistra.fr writes:
> If I understand correctly, the thread
> https://lists.gnu.org/archive/html/emacs-orgmode/2014-07/msg00678.html
> seems to say that variable
> 'org-list-empty-line-terminates-plain-lists' has been removed;
> consistently, querying it with 'C-h v' fails.
>
Hello.
If I understand correctly, the thread
https://lists.gnu.org/archive/html/emacs-orgmode/2014-07/msg00678.html
seems to say that variable
'org-list-empty-line-terminates-plain-lists' has been removed;
consistently, querying it with 'C-h v' fails.
Yet, it is still mentioned in the manual,
Hello,
James Harkins writes:
> On September 27, 2017 14:03:06 Eric S Fraga wrote:
>
>> On Wednesday, 27 Sep 2017 at 11:53, James Harkins wrote:
>>> Hi,
>>>
>>> There seems to be a mistake in the org-mode Ubuntu 16.02 packages.
>>>
>>> For beamer, if I
20 matches
Mail list logo