Re: certain files should not be folded
>>> "FE" == Fraga, Eric writes:
> On Friday, 24 Nov 2023 at 18:47, Uwe Brauer wrote:
>> Since I am not sure what are precisely these VISIBILITY properties,
> By VISIBILITY properties, I meant literally that: any properties
> labelled as VISIBILITY. But obviously you don't have any!
>> here is one example file
> which works just fine for me. What do you actually get?
--8<---cut here---start->8---
#+STARTUP: showeverything
#+title: nordstroem-field.tex
#+property: file-information ("a41dc43460f1abab60b8164d06bde036"
"/home/oub/ALLES/HGs//Pub/Preprints/Full-Euler-Nordstroem/"
"nordstroem-field.tex" 27975 "2023-11-14T17:35:14" immutable-location)
* Note..
--8<---cut here---end--->8---
--
I strongly condemn Hamas heinous atrocities on Israel, especially the
despicable pogroms.
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military.
I support the EU and NATO membership of Ukraine.
smime.p7s
Description: S/MIME cryptographic signature
Re: certain files should not be folded
On Friday, 24 Nov 2023 at 18:47, Uwe Brauer wrote: > Since I am not sure what are precisely these VISIBILITY properties, By VISIBILITY properties, I meant literally that: any properties labelled as VISIBILITY. But obviously you don't have any! > here is one example file which works just fine for me. What do you actually get? -- : Eric S Fraga, with org release_9.6.7-661-g34ee6f in Emacs 30.0.50
Re: certain files should not be folded
>>> "FE" == Fraga, Eric writes:
> The default is to show everything. Do you have an VISIBILITY properties
> in the file?
Since I am not sure what are precisely these VISIBILITY properties,
here is one example file
--8<---cut here---start->8---
#+STARTUP: showeverything
#+title: nordstroem-field.tex
#+property: file-information ("a41dc43460f1abab60b8164d06bde036"
"/home/oub/ALLES/HGs//Pub/Preprints/Full-Euler-Nordstroem/"
"nordstroem-field.tex" 27975 "2023-11-14T17:35:14" immutable-location)
* Note
Try to prove global existence for the Nordstroem equation, by *our* method,
but with a source generated by an irrotational fluid with a linear equation of
state
--8<---cut here---end--->8---
--
I strongly condemn Hamas heinous atrocities on Israel, especially the
despicable pogroms.
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military.
I support the EU and NATO membership of Ukraine.
smime.p7s
Description: S/MIME cryptographic signature
Re: certain files should not be folded
The default is to show everything. Do you have an VISIBILITY properties in the file? -- : Eric S Fraga, with org release_9.6.6-418-g294a4d in Emacs 30.0.50
certain files should not be folded
Hi I tried to follow https://orgmode.org/manual/Initial-visibility.html and put, for example, #+STARTUP: nofold or #+STARTUP: showall or #+STARTUP: showeverything But it did not work I close and open the file, but all headers are folded, what do miss here. Thanks Uwe Brauer -- I strongly condemn Hamas heinous atrocities on Israel, especially the despicable pogroms. I strongly condemn Putin's war of aggression against Ukraine. I support to deliver weapons to Ukraine's military. I support the EU and NATO membership of Ukraine.
Re: [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]
Sorry Ihor for the long delay. I got the error again for the second source block in the attached file. That is a sample of my configuration. Hope this helps, Andrea example.org Description: Lotus Organizer On Fri 13 Oct 2023 at 11:56, Ihor Radchenko wrote: > Andrea writes: > >> Thanks Ihor! I found out that there was (likely) an encoding issue on >> one of the source block. I had something like: >> :PROPERTIES: >> :ID: some-id >> :END: >> >> #+being_src emacs-lisp >> >> And trying to evaluate (org-babel-get-src-block-info 'no-eval) at the >> beginning of the source block was returning nil (as if I were outside of it). > > This should not happen. It would be nice if you can share a file with > problematic encoding, so that I could check if we have an edge case > with Org parser.
