Carlos Pita writes:
> When storing a <> or CUSTOM_ID link with org-store-link and then
> adding it with C-c C-l, org doesn’t ask for a description but automatically
> inserts an ugly description like:
>
> ~/Desktop/Org/captures.org::target
>
> or:
>
>
> The manual actually says
>
> "If this exists, it names packages on which the current package
> depends for proper operation."
>
> so I think it is reasonable to only list the minimum supported Emacs
> version, not the minimum version where it partially or fully works, but
> is not supported.
Tom Gillespie writes:
>> Please, keep ";; Package-Requires: " version in org.el consistent with
>> such statement (Should it be updated for the bugfix branch as well?).
>
> Unfortunately it is not clear that this is the right thing to do because
> nearly every feature of org may work on old
> Please, keep ";; Package-Requires: " version in org.el consistent with
> such statement (Should it be updated for the bugfix branch as well?).
Unfortunately it is not clear that this is the right thing to do because
nearly every feature of org may work on old versions. Should we put
users
> (while (process-live-p process)
> (accept-process-output process)))
When I tried this before it didn't work, but now it does, I
must have missed something. Patch updated accordingly.
The order in which the man.el code does things is supremely
confusing, but I think when accept-process-output
Max Nikulin writes:
> On 08/08/2022 22:46, Bastien wrote:
>> Ihor Radchenko writes:
>>
>>> Could you please elaborate on how exactly we can determine if a
>>> commit changes the compatibility status?
>> Today, we are interested in knowing whether Org is compatible with
>> Emacs 28.1, Emacs
Ihor,
thanks for your e-mail and explanation.
> We may clarify this in the manual.
probably worth doing. though, trying to describe it succinctly will be
a challenge, i think!
> Another alternative could be treating
> :results append drawer/code/pp/org/latex/html
> differently and putting
Hello Ypo,
Many thanks for sharing.
On Sunday, 7 Aug 2022 at 20:05, Ypo wrote:
> Hi Jeremie
>
> In my emacs it works great. Even org-fragtog that allows you to edit in
> an interactive manner.
Org impatient is also pretty nice :-)
https://github.com/yangsheng6810/org-latex-impatient
>
> - Just
Hi Max,
On Tuesday, 9 Aug 2022 at 23:31, Max Nikulin wrote:
> I had in mind :set attribute of defcustom, see info "(elisp) Variable
> Definitions"
I see. Thank you.
> In the particular case of `org-link-descriptive' some code should be
> executed *after* changing of its value.
Oh, okay, that
On 09/08/2022 22:46, Fraga, Eric wrote:
On Tuesday, 9 Aug 2022 at 22:21, Max Nikulin wrote:
Is it possible to use setter function for the defcustom to make the
following work?
I'm not sure what this means.
I had in mind :set attribute of defcustom, see info "(elisp) Variable
Definitions"
Hi Max,
On Tuesday, 9 Aug 2022 at 22:21, Max Nikulin wrote:
> Is it possible to use setter function for the defcustom to make the
> following work?
I'm not sure what this means.
> # Local Variables:
> # org-link-descriptive: nil
> # End:
Ah, thank you for pointing out the variable. I didn't
On 08/08/2022 22:46, Bastien wrote:
Ihor Radchenko writes:
Could you please elaborate on how exactly we can determine if a
commit changes the compatibility status?
Today, we are interested in knowing whether Org is compatible with
Emacs 28.1, Emacs 27.1 and Emacs Emacs 26.1.
Please, keep
András Simonyi writes:
> - cite/locators or cite/l to cite only the locators, and
THANK YOU for working on this! I have tried the "locators" style, and
it works great. At last, we can write in the APA style with no hacks!
P.S. Not a fan of using "ti" for the title. I would go for "T" for
On 08/08/2022 21:39, Juan Manuel Macías wrote:
I am attaching a patch with the documentation of the new variable in the
Manual and the updated NEWS.
+ =\babelprovide= command (see
+ http://mirrors.ctan.org/macros/latex/required/babel/base/babel.pdf).
+ Valid usage examples could be:
On 09/08/2022 21:50, Fraga, Eric wrote:
Once I've loaded an org file, I can
M-x org-toggle-link-display RET.
but I would like certain files to start up with links displayed.
If not already possible, it would be nice to either set a file local
variable or have, say:
#+startup:
Hello all,
Assuming I have not missed something, is there a variable I can set on
visiting an org buffer/file that ensures that links are displayed fully?
Once I've loaded an org file, I can
M-x org-toggle-link-display RET.
but I would like certain files to start up with links displayed.
András Simonyi writes:
> I've just noticed that there was a missing citeproc function
> declaration in oc-csl.el which could cause a compiler warning. The
> attached patch adds the required declaration.
Applied onto main via be7f61171.
Hi Ihor,
On Tuesday, 9 Aug 2022 at 20:39, Ihor Radchenko wrote:
> Can you please run M-x toggle-debug-on-error and share the full
> backtrace?
See below. I've not started investigating at all. The Julia REPL
buffer does get started so it's not an issue with Julia itself.
The backtrace below
Dear All,
I've just noticed that there was a missing citeproc function
declaration in oc-csl.el which could cause a compiler warning. The
attached patch adds the required declaration.
best wishes,
András
From e2573d8c858a280922f1dd13d2c49de9b74a9ec1 Mon Sep 17 00:00:00 2001
From:
OK, I was just about to hit "Send". My backtrace is the same.
-- Bill
On Tue, Aug 9, 2022 at 8:53 AM Fraga, Eric wrote:
> Hi Ihor,
>
> On Tuesday, 9 Aug 2022 at 20:39, Ihor Radchenko wrote:
> > Can you please run M-x toggle-debug-on-error and share the full
> > backtrace?
>
> See below.
Bill Burdick writes:
> OK, now I get this:
>
> ess-eval-buffer: Wrong type argument: symbolp,
> ((inferior-ess-primary-prompt . "\\w*> ") (inferior-ess-secondary-prompt)
> (inferior-ess-prompt . "\\w*> ") (ess-local-customize-alist .
> ess-julia-customize-alist) (inferior-ess-program .
Tom Gillespie writes:
> Hi Ihor,
>Here is an updated patch. We can't use accept-process-output
> because it doesn't seem to block in the way we need, or it blocks
> exactly long enough for the process to finish but then continues
> immediately to search instead of allowing the function that
András Simonyi writes:
> Dear All,
>
> On Sun, 7 Aug 2022 at 11:45, Ihor Radchenko wrote:
>
>> LGTM in general, but please add a proper commit message.
> [...]
>> Also, it would be useful to explain a bit what bibentry stands for.
>
> thanks, I've attached a new patch implementing these
>>> "CM" == Christian Moe writes:
> Hi, Uwe,
> Three ideas:
Wow, thanks a lot of all these solutions
I am using the new ods exporter found in
g...@github.com:kjambunathan/org-mode-ox-odt.git
And the first and the last solution work in the sense that LO can open the
exported ods file while
24 matches
Mail list logo
