Re: [O] data loss : org-mode 9 deletes encrypted entries if no pass is provided

[Nicolas Goaziou]

Hello,

fxiny  writes:

> old 8.2.10 left the entry unencrypted but untouched
> 9 deletes if the pass provided is none : a plain double pressed enter
>
> atm i'm running 9.0.3
> same problem with 0.1 and 0.2
>
> emacs version 25.1.90.1
>
> to reproduce : unencrypt , modify , save 
> no pass but press enter twice

Could you provide an ECM?

Regards,

-- 
Nicolas Goaziou

Re: [O] Something like #+BIND but for the destination buffer

[Nicolas Goaziou]

Hello,

Jonas Bernoulli  writes:

> I need to ensure that the texinfo exporter generates texi files that use
> space for indentation even when the global value of indent-tabs-mode is t.
> If tabs are used, then code blocks end up being intended wrong in the final
> info file.
>
> There are probably other more direct approaches to achieve this, but when I
> stumbled into #+BIND I thought I had found the mechanism to achieve this.
> But it turned out that #+BIND allows setting variables in the buffer from
> which the export happens, not the buffer into which it happens. So I would
> like to suggest the addition of something like #+BIND-DEST, to allow
> setting variables in the destination buffer.

Could you provide an ECM?

Besides, using `org-export-filter-final-output-functions' seems easier
than your set up.

Regards,

-- 
Nicolas Goaziou

Re: [O] Getting "Chapter" before a heading number

[Peter Davis]

On 12/31/16 9:23 AM, Nicolas Goaziou wrote:

Hello,

Peter Davis  writes:


Yes, thanks, Richard! This will certainly work for this occasion. It
would be great to find a way to do this through org in future,

As answered by Richard, the way to do this through Org is to use
a filter.


Aha! Thank you, Nicolas and Richard. I missed this in the earlier reply. 
I'll read up on it. Looks like a very powerful feature.


Thanks!
-pd

Re: [O] Getting "Chapter" before a heading number

[Nicolas Goaziou]

Hello,

Peter Davis  writes:

> Yes, thanks, Richard! This will certainly work for this occasion. It
> would be great to find a way to do this through org in future,

As answered by Richard, the way to do this through Org is to use
a filter.


Regards,

-- 
Nicolas Goaziou

Re: [O] bug in org parsing

[Nicolas Goaziou]

Hello,

Grégoire Jadi  writes:

> I've found what I think is a bug in orgmode parsing.
> When the following file is parsed :
> * Test
>
> #+BEGIN_SRC emacs-lisp :exports results :results raw drawer
> (format "* Test2")
> #+END_SRC
>
>
> #+RESULTS:
> :RESULTS:
> * Test2
> :END:

This syntax is incorrect. A drawer cannot contain a headline and "raw" +
"drawer" is an invalid combination. See `M-x org-lint' output.


Regards,

-- 
Nicolas Goaziou

Re: [O] Bug: emacs org-mode fail install with el-get when makeinfo --no-split org.texi -o org

[Nicolas Goaziou]

Hello,

Julio Molina Soler  writes:

> *Output with the error:*
> Done (Total of 115 files compiled, 3 skipped)
> /Library/Developer/CommandLineTools/usr/bin/make -C doc info
> org-version: 9.0.2 (release_9.0.2-132-gc130b2)
> makeinfo --no-split org.texi -o org
> org.texi:10468: @item outside of table or list
> make[1]: *** [org] Error 1
> make: *** [info] Error 2
>
> *To fix it:*
> $ emacs doc/org.texi
> line:10468
> 2 lines before
> Remove @end table
> add @end table at the end of the last item

This was fixed in Org 9.0.3. You may want to update Org.

Regards,

-- 
Nicolas Goaziou

[O] Something like #+BIND but for the destination buffer

[Jonas Bernoulli]

I need to ensure that the texinfo exporter generates texi files that use
space for indentation even when the global value of indent-tabs-mode is t.
If tabs are used, then code blocks end up being intended wrong in the final
info file.

There are probably other more direct approaches to achieve this, but when I
stumbled into #+BIND I thought I had found the mechanism to achieve this.
But it turned out that #+BIND allows setting variables in the buffer from
which the export happens, not the buffer into which it happens. So I would
like to suggest the addition of something like #+BIND-DEST, to allow
setting variables in the destination buffer.

I could then use something like

#+BIND-DEST: indent-tabs-mode nil

# Local Variables:
# org-export-allow-bind-keywords: t
# End:

to ensure that indent-tabs-mode is disabled. Currently I am using this

(defun ox-texinfo+--disable-indent-tabs-mode
(fn backend file-or-buffer
 async subtreep visible-only body-only ext-plist
post-process)
  (let ((saved-indent-tabs-mode (default-value 'indent-tabs-mode)))
(when (equal backend 'texinfo)
  (setq-default indent-tabs-mode nil))
(unwind-protect
(funcall fn backend file-or-buffer
 async subtreep visible-only body-only ext-plist
post-process)
  (setq-default indent-tabs-mode saved-indent-tabs-mode

(advice-add 'org-export-to-file   :around
'ox-texinfo+--disable-indent-tabs-mode)
(advice-add 'org-export-to-buffer :around
'ox-texinfo+--disable-indent-tabs-mode)


Thanks for considering

Re: [O] Getting "Chapter" before a heading number

[Peter Davis]

On 12/29/16 5:26 PM, Richard Lawrence wrote:

Hi Peter,

Peter Davis  writes:


I'm preparing a proposed table of contents for a book, and I'd like the HTML 
output to appear like:

Chapter 1 Blah
   1.1 blah
   1.2 blah blah
   1.3 blah blah blah

Chapter 2 Blah Blah
   2.1 blah
   2.2 blah blah

etc.

Is there a way to get HTML output to do this? I'd like the "*" at the start of 
a line to denote a new chapter, and nested headings
to go inside. I haven't been able to find anything like this.


This might not be exactly what you want, but it's pretty trivial to do
this with CSS.  In your stylesheet, you want something like (untested):

span.section-number-2:before { content: "Chapter" }

Basically, this tells the browser to put the word "Chapter" before the
number of a first-level headline (which, in a default setup, is exported
as a span tag with class section-number-2).

If you'd rather that "Chapter" appears in the actual HTML, you probably
want to use a filter on headlines during export.

Hope that helps!
Yes, thanks, Richard! This will certainly work for this occasion. It 
would be great to find a way to do this through org in future, for 
documents that keep changing, but this will work for now.


Thanks!
-pd

[O] bug in org parsing

[Grégoire Jadi]

Hi,

I've found what I think is a bug in orgmode parsing.
When the following file is parsed :
* Test
#+BEGIN_SRC emacs-lisp :exports results :results raw drawer
(format "* Test2")
#+END_SRC

#+RESULTS:
:RESULTS:
* Test2
:END:

The (truncated) result of `org-element-parse-buffer' is :
(src-block
 (:language \"emacs-lisp\" :switches nil :parameters \":exports results
:results raw drawer\" :begin 8 :end 98 :number-lines nil
:preserve-indent nil :retain-labels t :use-labels t :label-fmt nil
:value \"(format \\\"* Test2\\\")\\n\" :post-blank 1 :post-affiliated 8
:parent #2))
(paragraph
 (:begin 98 :end 119 :contents-begin 109 :contents-end 119 :post-blank 0
:post-affiliated 109 :results
 (\"\")
 :parent #2)
 #(\":RESULTS:\\n\" 0 10
   (:parent #3)))

That is, it generates a PARAGRAPH which seems incorrect.

However, when the following file is parsed :

* Test
#+BEGIN_SRC emacs-lisp :exports results :results raw drawer
(format "- Test2")
#+END_SRC

#+RESULTS:
:RESULTS:
- Test2
:END:

The truncated result of `org-element-parse-buffer' is :
(src-block
 (:language \"emacs-lisp\" :switches nil :parameters \":exports results
:results raw drawer\" :begin 8 :end 98 :number-lines nil
:preserve-indent nil :retain-labels t :use-labels t :label-fmt nil
:value \"(format \\\"- Test2\\\")\\n\" :post-blank 1 :post-affiliated 8
:parent #2))
(drawer
 (:begin 98 :end 133 :drawer-name \"RESULTS\" :contents-begin 119
:contents-end 127 :post-blank 0 :post-affiliated 109 :results
 (\"\")
 :parent #2))

That is, it generates a DRAWER, which seems correct.

WDYT?



signature.asc
Description: OpenPGP digital signature

[O] bug when generating org text then exporting to html

[Grégoire Jadi]

Hi all,

With the following file :
* Test
#+BEGIN_SRC elisp :results drawer :exports results
(format "* My Headline")
#+END_SRC


When I export this file to HTML, I expect to have the same result as if
I had the following file :
* Test
* My Headline

However, the exporter also include a paragraph with :RESULTS:.

WDYT?

I'm using Org mode version 9.0.3 (release_9.0.3-134-g517fed).



signature.asc
Description: OpenPGP digital signature

[O] data loss : org-mode 9 deletes encrypted entries if no pass is provided

[fxiny]

old 8.2.10 left the entry unencrypted but untouched
9 deletes if the pass provided is none : a plain double pressed enter

atm i'm running 9.0.3
same problem with 0.1 and 0.2

emacs version 25.1.90.1

to reproduce : unencrypt , modify , save 
no pass but press enter twice

[O] Bug: emacs org-mode fail install with el-get when makeinfo --no-split org.texi -o org

[Julio Molina Soler]

*Output with the error:*
Done (Total of 115 files compiled, 3 skipped)
/Library/Developer/CommandLineTools/usr/bin/make -C doc info
org-version: 9.0.2 (release_9.0.2-132-gc130b2)
makeinfo --no-split org.texi -o org
org.texi:10468: @item outside of table or list
make[1]: *** [org] Error 1
make: *** [info] Error 2

*To fix it:*
$ emacs doc/org.texi
line:10468
2 lines before
Remove @end table
add @end table at the end of the last item


-- 
Saludos Digitales,
Julio Molina Soler

jmolin...@gmail.com

Re: [O] Stuck projects documentation suggestion

[Jon Kristensen]

On 11/14/2016 12:32 PM, Nicolas Goaziou wrote:

Hello,

Jon Kristensen  writes:


Looking at http://orgmode.org/manual/Stuck-projects.html>, it wasn't
clear to me that "+PROJECT/-MAYBE-DONE" was something called a "match
syntax". If the documentation could be extended to include this
information, and a link to the matching tags and properties page, it
would be more understandable for new users.

Isn't it already done in the footnote in the page above?

Would you want to suggest a better wording for this page?


Sorry for the late reply!

I think it looks alright now. :)


The docstring for "org-stuck-projects" does include a reference to the
match syntax. (However, "C-h v" (describe variable) didn't work for
"org-stuck-projects" for me until I loaded "org-agenda", which was
surprising from my perspective as a newbie.)

It should probably be renamed to `org-agenda-stuck-projects' then.

Regards,

[O] bug when generating org text then exporting to html

[Grégoire Jadi]

Hi all,

With the following file :
* Test
#+BEGIN_SRC elisp :results drawer :exports results
(format "* My Headline")
#+END_SRC


When I export this file to HTML, I expect to have the same result as if
I had the following file :
* Test
* My Headline

However, the exporter also include a paragraph with :RESULTS:.

WDYT?

I'm using Org mode version 9.0.3 (release_9.0.3-134-g517fed).



signature.asc
Description: OpenPGP digital signature

Re: [O] Bug: org-publish-get-project-from-filename raises (wrong-type-argument sequencep any)

[Nicolas Goaziou]

Hello,

Arun Isaac  writes:

> Perhaps, `org-publish-get-project-from-filename' can be rewritten
> without `catch' and `throw' using `cl-some' or `seq-some'. This is not a
> bug. But, it might help improve readability of the logic.

Done. Note that `seq-some' is not an option since we support Emacs 24.3
and onwards.

I also fixed couple of issues in the function.


Regards,

-- 
Nicolas Goaziou