Bruno BEAUFILS skrev: (15 februari 2023 21:38:55 CET)
>On Wed, Feb 15, 2023 at 09:34:21AM -1000, Thomas S. Dye wrote:
>> I often use the .tex file to track down compilation issues. I don't want
>> Org to delete it.
>
>I get your point. In that case the file must not be removed when the
>compilati
On Wed, 15 Feb 2023 10:08:47 -0500 Ihor Radchenko wrote ---
> Matt m...@excalamus.com> writes:
>
> > Checking the final result from the callback is trickier. The following
> > works, but requires advice (which could potentially persist beyond the
> > test) and a delay (which sl
Ah, my bad. Got confused. The output above set according to the properties
is correct.
Thanks a lot for the fast fix.
On Wed, Feb 15, 2023 at 11:26 PM Daniel Hubmann wrote:
> Thanks for the partial fix.
>
> Unfortunately there is still something strange going on as the last
> heading gets hidde
Thanks for the partial fix.
Unfortunately there is still something strange going on as the last heading
gets hidden. Added some more headings to demonstrate this better:
This is the unfolded file content:
* Heading Lvl 1
** Heading Lvl 2 with VISIBILITY content
:PROPERTIES:
:VISIBILITY: content
reza writes:
> Hi Ihor
>
> Thanks for your quick reply
>
>> What you can do instead is creating a named Org paragraph with macro,
>> like
>>
>> #+name: year
>> {{{year}}}
>
> I tried this approach but it does not seem to work either:
>
> "template.org":
>
>#+TITLE: Report
>#+NAME: year
>
> It works, but Org does not include variable assignments to exported code
> by default. See org-babel-exp-code-template. The assignment would be
> done if you execute the blocks though.
So I have to set this variable to true?
> Note that year will have a value of "2019\n" with trailing newline.
reza writes:
>> What you can do instead is creating a named Org paragraph with macro,
>> like
>>
>> #+name: year
>> {{{year}}}
>
> I tried this approach but it does not seem to work either:
It works, but Org does not include variable assignments to exported code
by default. See org-babel-exp-co
Hi Ihor
Thanks for your quick reply
> What you can do instead is creating a named Org paragraph with macro,
> like
>
> #+name: year
> {{{year}}}
I tried this approach but it does not seem to work either:
"template.org":
#+TITLE: Report
#+NAME: year
{{{year}}}
* My headline
#+
Bruno BEAUFILS writes on Wed 15 Feb 2023 21:38:
> In all other (more numerous) cases (when everything went well) what
> is the point to have this file in addition to the source and the
> output?
Sometimes I select a part of the .tex and send it to someone who does
not use Org mode, for inclusi
reza writes:
>#+BEGIN_SRC bash :file log_{{{year}}}.csv
> ./get_log_file --start={{{year}}}-01-01 --end={{{year}}}-12-31
>#+END_SRC
>
>#+BEGIN_SRC python
> log = pd.read_csv("log_{{{year}}}.csv")
>#END_SRC
> ...
> But that does not seem to work. It looks like the macro e
On Wed, Feb 15, 2023 at 09:34:21AM -1000, Thomas S. Dye wrote:
> I often use the .tex file to track down compilation issues. I don't want
> Org to delete it.
I get your point. In that case the file must not be removed when the
compilation failed.
In all other (more numerous) cases (when everythi
Bruno BEAUFILS writes:
> When using the org-latex-export-to-pdf on any foo.org file I get the
> foo.pdf file produced the right way but I also get the foo.tex file.
>
> I think that the whole point of exporting to pdf is only to get the pdf
> file, avoiding the need to keep the latex one.
>
> I g
Hi List
I have the following setup:
In "template.org" is the structure of a report defined which I need to
generate for several years, e.g:
#+TITLE: Report
* My headline
#+BEGIN_SRC bash :file log_{{{year}}}.csv
./get_log_file --start={{{year}}}-01-01 --end={{{year}}}-12-31
#+
Rudolf Adamkovič writes:
> P.S. It took me a while to get all this because I do not use (nor have, for
> that
> matter) arrow keys, and those nonsensical function names mean absolutely
> nothing
> to me.
If you have ideas about good alternative names for these functions,
please share them.
--
Bruno BEAUFILS writes:
[[PGP Signed Part:Undecided]]
When using the org-latex-export-to-pdf on any foo.org file I get
the
foo.pdf file produced the right way but I also get the foo.tex
file.
I think that the whole point of exporting to pdf is only to get
the pdf
file, avoiding the need
When using the org-latex-export-to-pdf on any foo.org file I get the
foo.pdf file produced the right way but I also get the foo.tex file.
I think that the whole point of exporting to pdf is only to get the pdf
file, avoiding the need to keep the latex one.
I guess that one of org-latex-compile or
Ihor Radchenko writes:
> They indeed do not. Only on selected list items. Patches welcome!
Oh, wait I see. Non-recursive manipulation (l/r) works with marked regions but
recursive manipulation (L/R) does not work yet. Then, it all behaves correctly
and "patches welcome" makes sense (to make it
Max Nikulin writes:
> Since content of subr-x.el consists of `defsubst' definitions, likely it
> is preferable to use
>
> (eval-when-compile (require 'subr-x))
All right, I added the 'require' to both files. Better?
Rudy
>From 384515548a4eb790e9b947e484dd9da41bdece94 Mon Sep 17 00:00:00
On 2023-02-15, at 11:31, Angel de Vicente
wrote:
> Hello,
>
> Angel de Vicente writes:
>
>> Anybody knows off the top of your head how to toggle this?
>
> Sorry for the noise. "G" is the magic letter I was looking for.
And you could have found it out yourself with `C-h l' (`view-lossage').
`
Hemma thanks, for some reason, my Emacs does not display the link but it
does for other functions. Strange.
Thanks for the help!
Originalmeddelande
Från: Bruno Barbier
Datum: 2023-02-15 14:18 (GMT+01:00)
Till: Arthur Miller
Kopia: Ihor Radchenko , emacs-orgmode@gnu.org
Ä
Daniel Hubmann writes:
> * Heading Lvl 1...** Heading Lvl 2 with VISIBILITY content...
> *** Heading Lvl 3...
Thanks for reporting!
Fixed, on bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=be9280f68
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about
Jean Louis writes:
> That is not same case as Ihor, when he designated it as
>
> 2030-02-09 12:00 -0800 @UTC
> because there are no offsets @UTC time zone.
I do not recall providing such example. May you point me to the message
where you saw me writing -0800 @UTC?
--
Ihor Radchenko // yantar9
Ilya Chernyshov writes:
> So, we either should change the behavior of
> (org-element-timestamp-parser) or update the definitions of
> timestamp
> and timestamp range in org-manual. What do you think?
Updating the manual will make more sense. Would you mind writing a patch?
--
Ihor Radchenko /
Matt writes:
> Checking the final result from the callback is trickier. The following
> works, but requires advice (which could potentially persist beyond the test)
> and a delay (which slows testing overall and whose duration likely depends on
> the hardware the test runs on). Without the
Fraga, Eric writes on Wed 15 Feb 2023 12:30:
> I think this is indeed likely to be the reason.
Thanks for the confirmation. I was hoping that someone can arrange so
that the self explanatory message is shown each time, not the cryptic
one :-)
--
EOST (École et Observatoire des Sciences de la
Arthur Miller writes:
>
> Anyway, a follow question: Where is the source code?!
lisp/textmodes/string-edit.el
> Normally the help window says "... is a Lisp function in ."
>
My Emacs tells me it's an autoloaded function with the usual link.
Bruno
Ihor Radchenko writes:
> Arthur Miller writes:
>
>> Based on a Reddit thread:
>>
>> https://www.reddit.com/r/emacs/comments/10xhvd8/a_little_readstring_utility_using_an_org_mode/j7xziao/?context=3
>>
>> I did a small experiment to see if I can re-use org-capture, to just capture
>> a
>> string
I am having several issues with the fontification of emphasis markers in
org-special-blocks and inside latex equations in my org-files.
I have changed `org-emphasis-regexp-components` to be the following...
```
(with-eval-after-load 'org
(setcar org-emphasis-regexp-components "\t('\"{[:alph
On Wednesday, 15 Feb 2023 at 13:15, alain.coch...@unistra.fr wrote:
> did I understand what I presume is the reason:
>
>reftex-access-scan-info: RefTeX works only in buffers visiting a file
I think this is indeed likely to be the reason.
Similar issues arise with, for instance, ledger in that
Issued after 'org-edit-special' within a latex block (like the one
below) the command 'reftex-toc' generates the dreadful
reftex-TeX-master-file: Wrong type argument: stringp, nil
Only after some debugging time and trying
reftex-label
did I understand what I presume is the reason:
r
Hello Angel,
Angel de Vicente :
> I was too quick on the keyboard and I pressed some magic key combination
> and now my schedule for today shows in a compact way (only showing the
> appointments). I actually prefer the "expanded" way, in which I get a
> grid for the whole day (so it easier for me
Hello,
Angel de Vicente writes:
> Anybody knows off the top of your head how to toggle this?
Sorry for the noise. "G" is the magic letter I was looking for.
Cheers,
--
Ángel de Vicente -- (GPG: 0x64D9FDAE7CD5E939)
Research Software Engineer (Supercomputing and BigData)
Insti
Hello,
I was too quick on the keyboard and I pressed some magic key combination
and now my schedule for today shows in a compact way (only showing the
appointments). I actually prefer the "expanded" way, in which I get a
grid for the whole day (so it easier for me to quickly see if an
appointment
Tried (setq org-fold-core-style 'overlays) which is mentioned in the link.
Unfortunately the behaviour is still the same.
On Tue, Feb 14, 2023 at 10:15 PM William Denton wrote:
> On 14 February 2023, Bruno Barbier wrote:
>
> > Daniel Hubmann writes:
> >
> >> After using org-cycle-overview (or o
34 matches
Mail list logo
