Ihor Radchenko writes on Tue 28 Nov 2023 08:34:
> ... except when institution also prohibits anything but MS Outlook
> to access the MS Exchange protocol. In such dire scenario, the only
> option left is redirecting all the emails to another email provider
> that can be accessed via MSTP.
Ihor Radchenko writes on Fri 17 Nov 2023 09:22:
> I think that I need to clarify here.
Thank you.
Well, thank you for _trying_: most of the discussion in this thread is
way beyond my pay grade.
At the most basic user level (i.e., non lisp aware), why is it not
necessarily a bug if "something"
Matt writes on Thu 16 Nov 2023 20:03:
>
> On Thu, 16 Nov 2023 10:30:59 +0100 Ihor Radchenko wrote ---
>
> > Or we can make use of TRAMP as we usually do to access remote
> > environment. IMHO, it is more reliable as TRAMP takes care about
> > arranging all the Elisp FS
Matt writes on Mon 6 Nov 2023 19:01:
> I want to confirm, are you able to accomplish your task by using
> '-n'?
Yes. Evaluating this block (with C-c C-c):
#+begin_src bash :results output
ssh -n coch...@fruc.u-strasbg.fr "echo foo>foo_file"
echo "bar"
#+end_src
gives
Ihor Radchenko writes on Thu 26 Oct 2023 13:44:
> I can now reproduce the problem locally.
>
> It boils down to
>
> (setq exit-status
>(process-file shell-file-name input-file
> (if error-file
> (list t error-file)
>
Russell Adams writes on Thu 26 Oct 2023 16:44:
> [...] are you using an SSH key to connect, or entering a password?
> If you use an SSH key for passwordless access, try adding -n (ie:
> "ssh -n derp@host mycommand").
Yes, I use an SSH key, and yes, '-n' saves the day. Thanks.
--
EOST
Ihor Radchenko writes on Thu 26 Oct 2023 08:44:
> I currently do not have a setup to test ssh commands,
Sorry if that's irrelevant: I realized that one can ssh to the *same*
machine.
Thanks much for the detailed explanations.
> It looks like an issue in comint-mode and the way that it is
> handling the temporary ssh session. This is not an issue with
> org-mode.
So it is an issue with emacs, right?
--
EOST (École et Observatoire des Sciences de la Terre)
ITE
Hello.
For me, 'C-c C-c' on the following group
#+begin_src bash :results output
echo "foo"
echo "bar"
#+end_src
works as I expect: 'foo' and 'bar' are echo'ed. But it fails on this
one:
#+begin_src bash :results output
ssh coch...@fruc.u-strasbg.fr "echo foo>foo_file"
Hello. For internal links, the manual states that
To insert a link targeting a headline, in-buffer completion can be
used. Just type a star followed by a few optional letters into the
buffer and press ‘M-’. All headlines in the current buffer
are offered as completions."
Is
Ihor Radchenko writes on Sun 3 Sep 2023 07:58:
> 3. We require no less than 15 stars to define inlinetask, which
>looks ugly.
With org-indent-mode, only 2 stars are shown (which I don't find
ugly). Hence an idea: how about an additional
org-indent-mode-just-for-inlinetasks?, for those
Russell Adams writes on Wed 30 Aug 2023 16:31:
> > What would be the equivalent of:
> >
> >* head :foo:
> >*** inlt :bar:
> >*** END
> >
> > where the 'bar' tag could be used in exactly the same way as the 'foo'
> > tag.
> Please give some examples of
Russell Adams writes on Wed 30 Aug 2023 14:36:
> On Wed, Aug 30, 2023 at 01:49:26PM +0200, alain.coch...@unistra.fr wrote:
> > Russell Adams writes on Tue 29 Aug 2023 15:00:
> > > On Sat, Aug 26, 2023 at 08:01:16PM +0200, Russell Adams wrote:
> > > > Why not just put the TODO heading in a
Russell Adams writes on Tue 29 Aug 2023 15:00:
> On Sat, Aug 26, 2023 at 08:01:16PM +0200, Russell Adams wrote:
> > Why not just put the TODO heading in a code block with type org?
> >
> > Then you get all the toys, ignored by the main file.
>
> If inline tasks are supposed to be Org
Ihor Radchenko writes on Mon 27 Mar 2023 11:19:
> alain.coch...@unistra.fr writes:
>
> > Maybe it is normal, but if I put the cursor anywhere in the 1st line
> > (say) of this table
> >
> > ||---+---|
> > || x | x |
> >
> > and press , it becomes
> >
> > | | ---+--- | |
> > | |
Maybe it is normal, but if I put the cursor anywhere in the 1st line
(say) of this table
||---+---|
|| x | x |
and press , it becomes
| | ---+--- | |
| | x | x |
which is not what I would expect.
By contrast, if on this one
|---|+---|
| x || x |
it becomes
|---+---+---|
|
Ihor Radchenko writes on Mon 13 Mar 2023 11:29:
> Would you be interested to create a patch?
I wish I could, but it is beyond my ability: I am not an (e)lisp
programmer.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.coch...@unistra.fr
5
Dieter Faulbaum writes on Mon 13 Mar 2023 00:24:
>
> If you are prompted for the date, you can give a point ('.') and
> the current date is shown.
> I think this is "short enough".
Indeed, short enough. Thank you.
I guess I should have found it by myself, but skim reading through
8.2.1
Hello.
The manual says that
"When point is at an existing timestamp in the buffer, ['C-c .'
(‘org-time-stamp’)] is used to modify this timestamp instead of
inserting a new one."
but the default value is the existing date, not the current one so it
is not convenient at all for me.
In fact, I
Fraga, Eric writes on Fri 24 Feb 2023 08:06:
> On Thursday, 23 Feb 2023 at 16:25, Rob Sargent wrote:
> > Looks to me like this only happens if the last word of the line is
> > "emphasized" and larger font.
>
> This is not an org problem; it's LaTeX. It's happening because LaTeX
> has a
I only recently discovered subtree export, which I thought would be
better suited for me, but I have trouble to switch.
Consider the following file:
#+SELECT_TAGS: export conditional
#+EXCLUDE_TAGS:
#+OPTIONS: toc:nil title:nil author:nil date:nil tags:nil
* I :export:
** 1
Ihor Radchenko writes on Mon 20 Feb 2023 10:07:
> I looked further, and the situation is not as simple.
> https://grammarhow.com/backend-back-end-or-back-end/, for example,
> claims that only "back-end" is grammatically correct.
>
> I am now thinking to do the following:
> 1. Use "backend"
alain.coch...@unistra.fr writes on Fri 17 Feb 2023 07:49:
> I have sent a message to bug-auc...@gnu.org.
I got answers. See this thread:
https://lists.gnu.org/archive/html/bug-auctex/2023-02/threads.html#00035
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre &
Ihor Radchenko writes on Thu 16 Feb 2023 15:06:
> As the docstring states, the check is performed at point. Checking
> the actual modifications would be rather tricky. It might be done,
> but there are so many caveats that the code will be fragile.
OK, too bad. Thanks for trying.
--
Ihor Radchenko writes on Thu 16 Feb 2023 13:00:
> I'd say that it is reftex bug. It is generally expected that major
> modes do work in non-file buffers in Emacs.
Thanks. I have sent a message to bug-auc...@gnu.org.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut
Bruno BEAUFILS writes on Thu 16 Feb 2023 11:03:
> OK but you still can do this by just export the file to LaTeX
> (buffer or file) when needed.
In general, I want to see the final result, if only to check that it
is correct latex (as far as I can see, any crap is happily transformed
into a
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
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
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:
Ihor Radchenko writes on Sun 12 Feb 2023 15:23:
> [...] I want to implement more generic feature.
> See the attached patch.
This sounds very promising. I find the doc and the two relevant
docstrings clear.
However, I could not have it work for my case so far. I tried to add
"(undo .
Ihor Radchenko writes on Sat 11 Feb 2023 18:22:
> We can indeed at such warning, but it will probably be not very
> helpful.
I don't understand this. And isn't it better to have a more accurate
manual anyway?
Apart from that, since the default value in 9.6 is 'smart' ('nil' in
9.5), I wonder
Ihor Radchenko writes on Fri 10 Feb 2023 09:56:
> Only a handful of interactive commands support invisible edit
> checks. In particular: self-insert-command (typing), deleting char
> forward/backward, and `org-meta-return'.
>
> I guess we may instead provide a defcustom and hook the check
Hello. The documentation (version 9.6) says:
2.2.3 Catching invisible edits
--
Sometimes you may inadvertently edit an invisible part of the
buffer and be confused on what has been edited and how to undo the
mistake. Setting
Ihor Radchenko writes on Thu 2 Feb 2023 10:56:
> I am unable to reproduce on the latest main.
Me neither...
In addition to the initial release_9.6-204-g2f7052, I can still
reproduce with release_9.6-149-g554935.dirty, release_9.6-118-g04d2cc,
release_9.6-90-gf49ee9.dirty. But it's not on
I have noticed by chance that files with the .org.bak extension are in
Org mode by default.
If one does not pay attention, it can lead to mistakes.
If it is really intended, why not mention it in the manual? (In 1.3,
where it is said that "Files with the ‘.org’ extension use Org mode by
Hello. Reporting in case it is just a symptom that might
resurface in a realistic context.
With release_9.6-204-g2f7052.
I have file consisting only of
#+options: toc:nil author:nil date:nil
* foo
* bar
I put the point on the 'foo' line and do 'C-c C-e C-s l o'. The pdf
generated
Krishna Jani writes on Sat 7 Jan 2023 12:41:
>
> Hello,
>
> I have never had to write in languages other than English but an
> assignment just came up to transcribe the Indian Penal Code in
> simple and understandable Hindi. I have an Org file with some of my
> transcriptions (because of
Leo Butler writes on Fri 6 Jan 2023 22:52:
> It would be a simple matter to create a filter to insert that
> property drawer under the heading that contains point.
Well, feel free to enlighten me: I don't have any idea of even
how/where to start, but often face similar challen... err, simple
release_9.6-193-g30314c
I have file '~/Org/test.org', which contains
#+begin_src org
* foo
bar
#+end_src
I do 'C-c '' from within the src block, then 'C-c C-e l o' from the
*Org Src test.org[ org ]* buffer.
The minibuffer asks for an output file:
Output file: ~/Org/
I
Leo Butler writes on Fri 6 Jan 2023 21:38:
> Hello,
>
> I am trying something new this semester: all my lecture notes are
> organized into a single org file. A minor problem: I want to export each
> lecture (see below) as a separate pdf file. I would like to know if
> anyone has ``solved''
Pedro Andres Aranda Gutierrez writes on Fri 6 Jan 2023 13:10:
> Calling with `emacs -Q` on the following MWE:
>
> ```
> #+TITLE: Test
> #+SUBTITLE: MWE for section* bug
> #+LATEX_CLASS: article
> # +LATEX_CLASS: scrreprt
> #+LATEX_CLASS_OPTIONS:
Max Nikulin writes on Wed 4 Jan 2023 18:53:
> I suppose, the idea is to invoke it like
>
> C-u M-x org-insert-drawer
Yes, I got it.
Let me enlarge the scope (hence the new title). The manual says, in
1.5 Typesetting Conventions Used in this Manual (Key bindings and
commands):
In
Max Nikulin writes on Thu 5 Jan 2023 22:00:
> Sometimes I start emacs in a terminal application to copy some
> "special" text (holding [Shift]).
Great! It worked for the *Org Select* buffer.
I did not know that trick.
Thanks.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE
Ihor Radchenko writes on Thu 5 Jan 2023 11:07:
> However, I doubt that you can make much use of the buffer itself -
> it is nothing but text.
Without my suggesting that anything at all should be done, I am
commenting that sometimes one might need that text, if only for
personal notes, and it
Tim Cross writes on Thu 5 Jan 2023 09:43:
> As a simple example, try increasing the font size and see what
> happens to the menus. Keep in mind that some users require a very
> large font (for example, I use a 26 or 28 pt font.
OK, I understand. (Even with default font size, I hate that the
Bastien Guerry writes on Wed 4 Jan 2023 11:21:
> Strong +1 on working on Worg's styling.
>
> The task may be daunting, but we can also tackle it incrementally.
>
> >From memory, orgmode.org/worg is visited by ~30k persons each month,
> that 1000 persons per day. A patch enhancing the
release_9.6-193-g30314c
A right after 'M-x org-inlinetask-insert-task' adds a star to
the 15 already there; another , another star, and so on. Same
thing with cursor after a TODO keyword.
The behavior is the same if there is some content inside the
inlinetask (i.e., not on the 1st line).
--
With an org file like
* h
#+begin_export ascii
foo
#+end_export
putting the cursor on 'foo' and doing
M-x org-up-element
brings the cursor on '* h'. Same with the following blocks:
‘#+begin_comment’ ... ‘#+end_comment’
‘#+begin_example’ ... ‘#+end_example’
‘#+begin_export’
The manual (in 17.1) says that
After ‘#+’, [‘M-’] complete[s] the special keywords [...]
but if I do it after '#+EXP', it does not complete to
#+EXPORT_FILE_NAME:
Do I understand the manual incorrectly?
Thanks.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE
Ihor Radchenko writes on Sun 1 Jan 2023 13:23:
> I guess we can just make it into a command.
For me, that would be ideal. Otherwise, I think it would help a bit
to change the manual from
... this command calls ‘org-insert-property-drawer’ ...
to
... this command calls the non
Ihor Radchenko writes on Sun 1 Jan 2023 14:13:
> It is indeed Org 9.6 issue. Likely related to some obscure
> interaction between what Org does and `combine-after-change-calls'.
>
> Note that I am reporting for Emacs master, which ships with Org
> 9.6.
I'm afraid it is a bit complicated
> Confirmed.
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60467
Funny: since the problem was not present in previous versions of org,
I would have thought it was an org 9.6 issue...
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) |
The manual says:
You can interactively insert a drawer at point by calling
‘org-insert-drawer’, which is bound to ‘C-c C-x d’. [...] With a
prefix argument, this command calls ‘org-insert-property-drawer’,
which creates a ‘PROPERTIES’ drawer right below the current
headline.
Under release_9.6-173-g24740a
I have file
#+begin_src org
,* h1
,** h2
#+end_src
I do
M-x org-promote-subtree
on h2, which works as expected; then
M-x undo
The file becomes
#+begin_src org
,* h1
,** * h2
#+end_src
and I have the message
primitive-undo: Changes to be undone by
Ihor Radchenko writes on Thu 29 Dec 2022 10:04:
> This is to be expected because [...]
Thanks for taking the time to explain.
(I don't understand why you quoted the part of my message related to
things which work as expected, though.)
--
EOST (École et Observatoire des Sciences de la Terre)
alain.coch...@unistra.fr writes on Wed 28 Dec 2022 20:00:
> For example, for the file made of
>
>* foo @@latex:x x x x x x x x x x@@
>
> upon LaTeX export, the x's in are not in mathematical font.
So stupid of me. Sorry.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE
For example, for the file made of
* foo @@latex:x x x x x x x x x x@@
upon LaTeX export, the x's in are not in mathematical font.
PS: with release_9.6-149-g55493, after I hit 'C-c C-e l o', on the
file above, the following appears in the *Messages* buffer:
Invalid face reference:
Version used: release_9.6-149-g554935
With an org file containing only
#+begin_export latex
$x \text{foo $y$}$
\(x \text{foo \(y\)}\)
$x \text{foo \(y\)}$
\(x \text{foo $y$}\)
#+end_export
the pdf generated upon latex export gives as expected, i.e., with 'x'
and 'y' in
Ihor Radchenko writes on Tue 27 Dec 2022 13:43:
> Can you try the attached patch?
It did not work with the version I initially used:
release_9.6-149-g554935.dirty
but it works OK with
release_9.6-149-g554935
Thanks
--
EOST (École et Observatoire des Sciences de la Terre)
ITE
Tested with
Org mode version 9.6 (release_9.6-149-g554935.dirty @
/home/cochard/Org/Coch-git/org-mode/lisp/)
I have the file debug.org containing
* h1
foo
* h2
foo bar
I make the 1st two lines the region. Then I do
M-x org-agenda << / foo
and I see
2 matches for
Here is a minimal example: file debug2.org which contains
* foo
*** inlt
ininlt
*** END
bar
I run
emacs -Q -l ~/.emacs
where .emacs contains only
(require 'org-inlinetask)
and which gives
GNU Emacs 27.2 (build 1, x86_64-redhat-linux-gnu,
Hello.
I do
emacs -Q -l ~/.emacs.git
where the .emacs.git file contains only
(add-to-list 'load-path "~/Org/Coch-git/org-mode/lisp")
(require 'org-inlinetask)
This gives
Org mode version 9.6 (release_9.6-118-g04d2cc.dirty @
/home/cochard/Org/Coch-git/org-mode/lisp/)
GNU
Ihor Radchenko writes on Tue 13 Dec 2022 13:14:
> alain.coch...@unistra.fr writes:
>
> > I have a practical question, though: in order to see the effect of
> > your patch in context, I applied it in my git repository and did
> >
> >make && make doc
> >
> > I then can see the change in
Ihor Radchenko writes on Wed 14 Dec 2022 07:55:
> This particular note is largely aiming at new users not too
> familiar with Emacs system.
> [...]
> Note, however, that org-goto is probably not the only place where we
> refer to a customization that is not loaded by default. I am unsure
Max Nikulin writes on Wed 14 Dec 2022 17:01:
> On 13/12/2022 15:54, Alain.Cochard wrote:
> > At the end of section 2.3 (Motion) of the manual:
> >
> > See also the variable ‘org-goto-interface’.
> >
> > But this variable does not seem to exist.
>
> Alain, could you, please,
Ihor Radchenko writes on Tue 13 Dec 2022 11:43:
> Does the attached patch help with understanding?
Yes, for me this is perfectly clear.
I have a practical question, though: in order to see the effect of
your patch in context, I applied it in my git repository and did
make && make doc
I
Ihor Radchenko writes on Tue 13 Dec 2022 09:33:
> alain.coch...@unistra.fr writes:
>
> > At the end of section 2.3 (Motion) of the manual:
> >
> > See also the variable ‘org-goto-interface’.
> >
> > But this variable does not seem to exist.
>
> It does, but you need to load
At the end of section 2.3 (Motion) of the manual:
See also the variable ‘org-goto-interface’.
But this variable does not seem to exist.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.coch...@unistra.fr
5 rue René Descartes
Ihor Radchenko writes on Tue 13 Dec 2022 07:36:
> alain.coch...@unistra.fr writes:
>
> > NB: While experimenting, I noticed that, if I customize
> > org-cycle-max-level to 0, then a on a headline generates the
> > cryptic "org-match-line: Invalid regexp: "Invalid content of
> > \\{\\}"".
Anthony Carrico writes on Mon 12 Dec 2022 09:41:
> On 12/12/22 09:20, alain.coch...@unistra.fr wrote:
> > Perhaps you have in min >
> >'<', followed by a template selector and '
>
> Yes!
> Was this deprecated because it isn't a regular emacs keybinding?
I don't remember. It was
Anthony Carrico writes on Mon 12 Dec 2022 08:50:
> I'm trying to remember what the old keybinding was before it got
> switched to 'C-c C-,'...
Perhaps you have in mind
'<', followed by a template selector and '
?
See 17.2 Structure Templates:
For example, ‘< s ’ creates a code block.
Ihor Radchenko writes on Fri 25 Nov 2022 10:33:
> alain.coch...@unistra.fr writes:
> > I do not understand the last sentence, even assuming that the 1st
> > 'of' is 'or'. Is my English the problem?
>
> That sentence is indeed screwed up.
>
> Does `org-cycle-max-level' docstring sound
Colin Baxter writes on Thu 1 Dec 2022 11:19:
> You might have an INFOPATH conflict.
Indeed. Thanks.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.coch...@unistra.fr
5 rue René Descartes [bureau 110] | Phone: +33 (0)3 68 85 50 44
With the 9.5.5 version
Org mode version 9.5.5 (9.5.5-g8ef620 @
/home/cochard/.emacs.d/elpa/org-9.5.5/)
What I have in Info is
The Org Manual
**
This manual is for Org version 9.5.
Copyright © 2004–2022 Free Software Foundation, Inc.
But if
Org
alain.coch...@unistra.fr writes on Tue 29 Nov 2022 12:33:
> I would expect that the mistake be reported in the *Org PDF LaTeX
> Output* Compilation buffer. So far, what I saw in that buffer was
> essentially what shows up when I run 'pdflatex org_generated_file.tex'
> from a terminal. Not
Fraga, Eric writes on Tue 29 Nov 2022 11:16:
> I think having the expectation that org will parse within LaTeX
> blocks may be a little unrealistic.
Org, no, but (pdf)latex yes.
> But, also, what should it do?
I would expect that the mistake be reported in the *Org PDF LaTeX
Output*
Fraga, Eric writes on Tue 29 Nov 2022 10:40:
> You cannot use a subscript within \text{}.
Yes. My point was that Org did not spot this mistake and generates
something ridiculous.
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) |
I have file debug3.org which contains only
* strange
#+begin_export latex
\[
\text{a_b}
\]
#+end_export
Upon latex export (C-c C-e l o) the generated pdf shows a sequence of
4 "a subscript b" in a row (with 3 font sizes).
Result observed with various Org versions
The last paragraph of this docstring is:
It is strongly recommended that you set ‘org-cycle-max-level’ not
at all, or to a number smaller than this one. In fact, when
‘org-cycle-max-level’ is not set, it will be assumed to be one less
than the value of smaller than the value of
Ihor Radchenko writes on Tue 22 Nov 2022 08:16:
> See the attached patch with tentative changes to the manual. Let
> me know if you think that things are still not clear.
Things are clear. Thanks.
> +The result type detection depends on the code block language, as
> +described in the
Ypo writes on Wed 16 Nov 2022 20:20:
> Thanks, working!!
>
> I can't see those options in the manual (15.10.4 Query Replace)
How about 15.6 (Syntax of Regular Expressions)?
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) |
Ihor Radchenko writes on Mon 14 Nov 2022 03:59:
> alain.coch...@unistra.fr writes:
>
> > Ihor Radchenko writes on Mon 7 Nov 2022 02:31:
> > > If you want to force string output, use :results output.
> > >
> > > By default, ob-shell tries to guess the output type. In the
> > > case of
Ihor Radchenko writes on Mon 7 Nov 2022 02:31:
> If you want to force string output, use :results output.
>
> By default, ob-shell tries to guess the output type. In the case
> of two commands returning output, the guess is yielding the
> table. In the case of a single command, the guess
Ypo writes on Sat 12 Nov 2022 15:42:
> Hi
>
> I am copy-pasting e-books into org-mode to read and study them.
>
> Usually, words come hyphenated, like "ato- mized", that I wanted to
> transform into "atomized".
>
> I am trying with query replace, but I am starting to think that it is
Ypo writes on Fri 11 Nov 2022 13:49:
> Great!!
>
> Is it easy for a user to test if it works?
One possibility (provided git is installed on your system) is:
mkdir ~/Build/Emacs
cd ~/Build/Emacs
git clone https://git.savannah.gnu.org/git/emacs/org-mode.git
cd org-mode && make
Ihor Radchenko writes on Thu 10 Nov 2022 02:03:
> alain.coch...@unistra.fr writes:
>
> > > I recommend you to use :EXPORT_FILE_NAME: headline property and
> > > export using subtree scope.
> >
> > Thanks a lot for the tip. A suggestion: that the :TITLE:
> > property be used if it exists.
Hello.
I do
emacs -Q -l ~/.emacs.git
with .emacs.git being
(add-to-list 'load-path "~/Org/Coch-git/org-mode/lisp")
(custom-set-variables
'(org-babel-load-languages
'(
(shell . t))
)
'(debug-on-error t)
)
Org mode version 9.6-pre
> Fixed on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3e010d81dcabafcdd97199b8122491a74ad9cbed
Thanks a lot. I checked that the problem is no longer present for me
either.
> This is because the error terminated export process in the middle
> of it. Org
Hello.
I have this file:
#+STARTUP: fnlocal
* headline 1
1st call to footnote 1[fn:1]
[fn:1] footnote 1 body
* subtree to be exported
2nd call to footnote 1[fn:1]
call to footnote 2[fn:2]
[fn:2] footnote 2 body
* COMMENT commented headline
nothing
- 1st issue
alain.coch...@unistra.fr writes on Tue 11 Oct 2022 16:42:
> Ihor Radchenko writes on Sun 2 Oct 2022 12:48:
>
> > I recommend you to use :EXPORT_FILE_NAME: headline property and export
> > using subtree scope.
>
> Thanks a lot for the tip. A suggestion: that the :TITLE: property
> be
I do
emacs -Q -l ~/.emacs.debug
where .emacs.debug contains only
(custom-set-variables
'(org-agenda-files '("~/Org/my-agenda-debug.org"))
)
and my-agenda-debug.org contains only
* learn org at 12:00
DEADLINE: <2022-10-14 Fri 12:00>
Then I do
M-x org-agenda a
and
Ihor Radchenko writes on Sun 2 Oct 2022 12:48:
> I recommend you to use :EXPORT_FILE_NAME: headline property and export
> using subtree scope.
Thanks a lot for the tip. A suggestion: that the :TITLE: property be
used if it exists.
> > I can only hope that the "observed inconsistency"
Samuel Wales writes on Tue 28 Jun 2022 16:23:
> [inactive timestamps] much better than date trees for my case.
Reading this, I tried to find out what a date tree is.
The manual says (in 10.1.3.1):
A date tree is an outline structure with years on the highest
level, months or ISO weeks
Ihor Radchenko writes on Tue 27 Sep 2022 15:40:
> However `org-export-as' is generally called inside
> `org-export-to-file' and `org-export-to-file' needs to know which
> file to export to in advance; before the buffer is stripped of
> commented trees. That's why there is the observed
Thanks for answering.
Ihor Radchenko writes on Tue 27 Sep 2022 09:55:
> alain.coch...@unistra.fr writes:
>
> > Hello. I have the file:
> >
> >* COMMENT foo
> >#+EXPORT_FILE_NAME: foo.pdf
> >#+TITLE: foot
> >fofoo
> >* bar
> >#+EXPORT_FILE_NAME: bar.pdf
> >
Hello. I have the file:
* COMMENT foo
#+EXPORT_FILE_NAME: foo.pdf
#+TITLE: foot
fofoo
* bar
#+EXPORT_FILE_NAME: bar.pdf
#+TITLE: bart
babar
If I do 'C-c e l p', the file 'foo.pdf' is created from the 'foo.tex'
file. The content is bar'ish, though, as I expect.
By
Ihor Radchenko writes on Fri 9 Sep 2022 18:38:
> This is confusing. I actually can reproduce.
> [...]
> I did export using C-c C-e t A (ASCII to buffer)
Sorry, it did not occur to me that there is a life out of latex
export. I used C-c C-e l o. I can also reproduce with C-c C-e t A.
--
Dominik Schrempf writes on Fri 9 Sep 2022 11:08:
> Hello!
>
> When using the basic org cite export processor, that is:
>
> #+cite_export: basic
>
> bibliography items with curly braces are rendered in an unexpected way.
>
> [...]
>
> In particular, the curly braces are printed.
I
Ihor Radchenko writes on Wed 31 Aug 2022 09:57:
> This is not a bug. Just unintuitive syntax:
> [...]
> The important part is: It ends at the next footnote definition,
> headline, or after two consecutive empty lines.
>
> So, your example is
>
> foo[fn:1]
>
> [fn:1] bar
>
Hello. When I visit an org buffer containing only:
foo[fn:1]
[fn:1] bar
#+begin_example
x
#+end_example
then, hitting when the cursor is on either '#' does nothing
(i.e., no folding).
Tested with 'emacs -Q' and the following combinations:
GNU Emacs 27.2 (build 1,
1 - 100 of 213 matches
Mail list logo
