Re: [O] Tangling include files

[Charles C. Berry]

On Thu, 24 Nov 2016, Harry Butterworth wrote:


I tried org-org-export-to-org which puts everything into a single document
but it strips the :tangle parameters out so a subsequent tangle doesn't
generate any source code.



You might try this. Put this at the *top* of your file:

--8<---cut here---start->8---

#+PROPERTY: header-args :eval never-export

#+NAME: tangle file
#+BEGIN_SRC emacs-lisp :eval yes :exports results
(org-babel-tangle)
#+END_SRC

--8<---cut here---start->8---

Type C-c C-c on the property line to refresh it.

Now export. Type 'y' in reply to the query to eval the `tangle file' src 
block and again to the `discard edits' query.


Even exporting to a buffer should be fine. You do not really want the 
exported document, you just want to force the inclusions to take place and 
then run that src block.


This should work, because `org-export-as' will expand all the include's 
before running babel. If the above block runs before any others, then the 
:tangle headers will still be in place.


In fact you could create a separate file, place all the above in it and 
add one line at the bottom to include the top level org file you want to 
tangle from. Then export that.


HTH,

Chuck

Re: [O] Tangling include files

[Harry Butterworth]

I tried org-org-export-to-org which puts everything into a single document
but it strips the :tangle parameters out so a subsequent tangle doesn't
generate any source code.

On 23 November 2016 at 17:47, Marco Wahl  wrote:

> Hi!
>
> > I am attempting to switch from FunnelWeb to Org for literate
> > programming.  I'm stuck because I can't work out how to include .org
> files
> > and then tangle everything.  A tangle in the top level file only seems to
> > tangle the contents of that file and not the contents of the included
> files.
> >
> > I did find something on this topic in a mailing list from several
> years
> > back but the workaround posted there seems to be out of date.
> >
> > I don't want to put all my source code into one big .org file.  With
> > FunnelWeb, I would organize source code for public classes into an
> > interface file and an implementation file and private classes into a
> single
> > file so the resulting document could have a section documenting the
> public
> > API followed by the implementation.
> >
> > So the top level document would end up something like this:
> >
> > include X_int
> > include Y_int
> > include Z_int
> > include X
> > include Y
> > include Z
> > include P
> > include Q
> > include R
> >
> > It looks to me like there have been some changes around the
> implementation
> > of INCLUDE in Org, I'm wondering if tangling include files is now
> supported
> > and if so, how to do it.
> >
> > My installed Org version is 8.2.4 but obviously I'll upgrade if
> necessary.
>
> Quick thought: what about exporting the top level document as Org and
> then tangle the resulting (one big) .org file?
>
>
> HTH
>
> Morco
>
>
>

Re: [O] org.texi edits, patch attached

[Lambda Coder]

Nicolas, attached is the revised edits for:

* Working with source code (2nd review)
* Miscellaneous
* Hacking
* MobileOrg

The patch is against maint branch from today.

Best wishes,

--Lambda Coder

On Fri, Nov 18, 2016 at 8:09 PM, Lambda Coder  wrote:

> Thanks Nicolas for pushing the 1st set of edits.
>
> Attached I have a 2nd set of edits for the same chapter. Cleaned up
> references mainly.
>
> This patch is based off maint branch. Hope it's easier for you this time.
>
> Best wishes,
>
> --Lambda Coder
>
>
> On Fri, Nov 18, 2016 at 12:21 AM, Nicolas Goaziou 
> wrote:
>
>> Hello,
>>
>> Lambda Coder  writes:
>>
>> > Do you prefer future edits against master or maint branch? It was not
>> clear
>> > when I asked the very first time.
>>
>> Documentation fixes usually go to maint, unless they refer to
>> a master-only feature, obviously.
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>
>


0001.patch.gz
Description: GNU Zip compressed data

Re: [O] org-mode 9.0 LaTeX export figure labels do not work

[John Kitchin]

you might want to try:

(setq org-latex-prefer-user-labels t)


Arkady Grudzinsky writes:

> org-mode 9.0 seems to generate random figure labels instead of
> the ones specified in #+NAME:, so the cross-references do not work.
>
> .org source:
> ,
> | Temperature profile is shown in Fig. \ref{fig:tcprofile}.
> | 
> | #+NAME: fig:tcprofile
> | #+CAPTION: Temperature Cycling Profile
> | [[./tc_profile.png]]
> `
>
> .tex output:
> ,
> | Temperature profile is shown in Fig. \ref{fig:tcprofile}.
> | 
> | \begin{figure}[htbp]
> | \centering
> | \includegraphics[width=.9\linewidth]{./tc_profile.png}
> | \caption{\label{fig:orgceb3fa6}
> | Temperature Cycling Profile}
> | \end{figure}
> `
>
> PDF output:
>
> ,
> | Temperature profile is shown in Fig. ??.
> `
>
> Is this a new feature or a bug?


-- 
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

[O] [patch] Small bug fix to the python babel documentation

[Yuval Langer]

Fixing a very small bug in which a source block ends with `#+end_src
python` instead of `#+end_src`, prohibiting it from being recognized
as a source block.

The branch:
https://gitlab.com/yuvallanger/worg-mirror-unofficial/tree/fix-end-src-python

The commit:
https://gitlab.com/yuvallanger/worg-mirror-unofficial/commit/8f6214fe35199186f256c17cccecbd5a9a8063c7

Attached is the `git format-patch master` patch file while HEAD is
pointing at fix-end-src-python.

Many thanks,
Yuval Langer.
From 8f6214fe35199186f256c17cccecbd5a9a8063c7 Mon Sep 17 00:00:00 2001
From: Yuval Langer 
Date: Thu, 24 Nov 2016 00:47:18 +0200
Subject: [PATCH] Fix bad end_src

---
 org-contrib/babel/languages/ob-doc-python.org | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/org-contrib/babel/languages/ob-doc-python.org b/org-contrib/babel/languages/ob-doc-python.org
index 8acfbff..3ca20e1 100644
--- a/org-contrib/babel/languages/ob-doc-python.org
+++ b/org-contrib/babel/languages/ob-doc-python.org
@@ -191,7 +191,7 @@ plt.savefig('images/myfig.pdf')
 #+begin_example
 #+begin_src python :results output
 print "Hello, world!"
-#+end_src python
+#+end_src
 
 #+RESULTS:
 : Hello, world!
-- 
2.9.3

Re: [O] org-mode 9.0 LaTeX export figure labels do not work

[Arkady Grudzinsky]

On Wed, Nov 23 2016, Arkady Grudzinsky wrote:

> org-mode 9.0 seems to generate random figure labels instead of
> the ones specified in #+NAME:, so the cross-references do not work.

Figured out that the LaTeX reference syntax does not work
anymore.  But the org-mode reference [[fig:tcprofile]] does.  OK.
Makes sense.

>
> .org source:
> ,
> | Temperature profile is shown in Fig. \ref{fig:tcprofile}.
> | 
> | #+NAME: fig:tcprofile
> | #+CAPTION: Temperature Cycling Profile
> | [[./tc_profile.png]]
> `
>
> .tex output:
> ,
> | Temperature profile is shown in Fig. \ref{fig:tcprofile}.
> | 
> | \begin{figure}[htbp]
> | \centering
> | \includegraphics[width=.9\linewidth]{./tc_profile.png}
> | \caption{\label{fig:orgceb3fa6}
> | Temperature Cycling Profile}
> | \end{figure}
> `
>
> PDF output:
>
> ,
> | Temperature profile is shown in Fig. ??.
> `
>
> Is this a new feature or a bug?

-- 
Arkady

[O] org-mode 9.0 LaTeX export figure labels do not work

[Arkady Grudzinsky]

org-mode 9.0 seems to generate random figure labels instead of
the ones specified in #+NAME:, so the cross-references do not work.

.org source:
,
| Temperature profile is shown in Fig. \ref{fig:tcprofile}.
| 
| #+NAME: fig:tcprofile
| #+CAPTION: Temperature Cycling Profile
| [[./tc_profile.png]]
`

.tex output:
,
| Temperature profile is shown in Fig. \ref{fig:tcprofile}.
| 
| \begin{figure}[htbp]
| \centering
| \includegraphics[width=.9\linewidth]{./tc_profile.png}
| \caption{\label{fig:orgceb3fa6}
| Temperature Cycling Profile}
| \end{figure}
`

PDF output:

,
| Temperature profile is shown in Fig. ??.
`

Is this a new feature or a bug?


-- 
Arkady

Re: [O] Generating LaTeX SRC block during HTML export broken in 9.0.1

[Eric S Fraga]

On Tuesday, 22 Nov 2016 at 08:37, Éric Würbel wrote:

[...]

> When exporting to html file (C-x C-e h h) org complains :
>
> org-babel-exp process latex at position 358...
> executing Latex code block...
> Processing LaTeX file /tmp/babel-6122X0-/latex-6122U9y.tex...
> org-compile-file: File "/tmp/babel-6122X0-/latex-6122U9y.pdf" wasn't
> produced.  See "*Org PDF LaTeX Output*" for details
>
>
> And then :
> 1. *Org PDF LaTeX Output* contains no error at all
> 2. an output pdf file is generated
> 3. the png file ins not produced.
> 4. temporary files pollute the current directory

I can confirm all of the above.

Mind you, I did have to change the LaTeX to have \EndFunction instead of
\EndAlgorithm...

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.1-49-ga43eac

[O] color specific days in different background in org agenda

[Xebar Saram]

Hi all

a weird question. i want to be able to color specific days in different
background in org agenda so i have a nice visual queue to not schedule
meeting during theses days so i can focus on actual work :)

any clue if thats possible?

best

z

Re: [O] Tangling include files

[Marco Wahl]

Hi!

> I am attempting to switch from FunnelWeb to Org for literate
> programming.  I'm stuck because I can't work out how to include .org files
> and then tangle everything.  A tangle in the top level file only seems to
> tangle the contents of that file and not the contents of the included files.
>
> I did find something on this topic in a mailing list from several years
> back but the workaround posted there seems to be out of date.
>
> I don't want to put all my source code into one big .org file.  With
> FunnelWeb, I would organize source code for public classes into an
> interface file and an implementation file and private classes into a single
> file so the resulting document could have a section documenting the public
> API followed by the implementation.
>
> So the top level document would end up something like this:
>
> include X_int
> include Y_int
> include Z_int
> include X
> include Y
> include Z
> include P
> include Q
> include R
>
> It looks to me like there have been some changes around the implementation
> of INCLUDE in Org, I'm wondering if tangling include files is now supported
> and if so, how to do it.
>
> My installed Org version is 8.2.4 but obviously I'll upgrade if necessary.

Quick thought: what about exporting the top level document as Org and
then tangle the resulting (one big) .org file?


HTH

Morco

[O] Tangling include files

[Harry Butterworth]

Hi Folks,

I am attempting to switch from FunnelWeb to Org for literate
programming.  I'm stuck because I can't work out how to include .org files
and then tangle everything.  A tangle in the top level file only seems to
tangle the contents of that file and not the contents of the included files.

I did find something on this topic in a mailing list from several years
back but the workaround posted there seems to be out of date.

I don't want to put all my source code into one big .org file.  With
FunnelWeb, I would organize source code for public classes into an
interface file and an implementation file and private classes into a single
file so the resulting document could have a section documenting the public
API followed by the implementation.

So the top level document would end up something like this:

include X_int
include Y_int
include Z_int
include X
include Y
include Z
include P
include Q
include R

It looks to me like there have been some changes around the implementation
of INCLUDE in Org, I'm wondering if tangling include files is now supported
and if so, how to do it.

My installed Org version is 8.2.4 but obviously I'll upgrade if necessary.

Thanks

Harry

Re: [O] DEADLINE: position in entry

[Yasushi SHOJI]

Hi,

On Tue, Nov 22, 2016 at 3:08 AM, Sebastien Vauban 
wrote:
>
> Yasushi SHOJI  writes:
> >  >8  cut  >8 
> > * DONE org
> >   DEADLINE: [2016-01-07 Thu 17:39]
> >
> >   SCHEDULED: <2015-09-29 Tue .+1w>
> >
> >  >8  cut  >8 
>
> A shoot in the dark: replace the [] by <>.
>
> [] for DEADLINE does not make much sense...

thanks for your comment.
chainging the inactive timestamp to active doesn't seem
to change the behavior.

even with an inactive time stamp, it's not a good excuse
to show a closed entry, isn't it?
-- 
yashi