Hi
I thought this worked a while ago, but in a gnus article buffer I tried to use
org-store-link and received
(Running Emacs Master and org-mode master (some weeks old))
Debugger entered--Lisp error: (void-function org-fixup-message-id-for-http)
org-fixup-message-id-for-http("8ad92378cff62
Apologies for the book. I've been sitting on this stuff for two months and am
wondering how to proceed.
IANAL but AFAIK/CT, my contract contains an exception for making contributions
to projects like Org. I've gotten confirmation from my manager and by HR.
However, until the CEO signs the FSF
Eduardo Suarez-Santana writes:
>> I am unable to reproduce. What are your Org and Emacs versions?
>
> I'm using Spacemacs (develop branch).
>
> - Emacs 27.2
> - Org 9.5.1
>
> I get a weird behaviour about it. These events appear when I start emacs. If I
> edit somehow these entries they disappear
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
"Berry, Charles" writes:
> Max,
>
>> On Dec 31, 2021, at 4:05 AM, Max Nikulin wrote:
>>
>>
>> Should some function a macro be provided to facilitate declaring
>> languages as data format (config files, JSON, YAML, etc.) rather than
>> executable source code?
>
> I think we already have this in
Max Nikulin writes:
> On 30/12/2021 15:00, Rudolf Adamkovič wrote:
>>
>> #+property: header-args:bibtex+ :eval yes
>
> Why do you set ":eval yes" explicitly for bibtex if you believe that
> it should not be executed?
Plain old stupidity. :)
Rudy
--
"Programming reliably --- must be an activi
On Sat, Jan 01, 2022 at 11:10:30PM +0800, Ihor Radchenko wrote:
> Eduardo Suarez writes:
>
> > The next code snippet makes the entry to appear in the agenda:
> >
> > * sample date code
> > #+begin_src org
> > SCHEDULED: <2015-02-16 Mon .+2d>
> > #+end_src
>
> I am unable to reproduce. What are y
Dear All,
On Sat, 1 Jan 2022 at 14:53, Julien Chastang
wrote:
> I have been experimenting with org-cite. I noticed that I can insert
> (org-cite-insert) all bibtex types *except* for @conference. [...]
> yet I believe @conference is a valid bibtex type. I noticed that
> org-bibtex-types has an
There appears to be confusion between "org-journal-new-entry" and
"org-goto". My ME is:
1. emacs -Q (I used emacs-29.0.50)
2. M-x load-library
3. /path/to/org-journal.el
4. C-h c
5. C-c C-j
6. "C-c C-j runs the command org-journal-new-entry"
7. Create an org file (say "test.org") from C-x C-
Eduardo Suarez writes:
> The next code snippet makes the entry to appear in the agenda:
>
> * sample date code
> #+begin_src org
> SCHEDULED: <2015-02-16 Mon .+2d>
> #+end_src
I am unable to reproduce. What are your Org and Emacs versions?
> Any hint?
Update org?
> On the other hand, I wonder
Jack Kamm writes:
> Hi Christopher,
>
>> This might need to mentioned in Org manual and in ob-python.el source
>> code with comment. WDYT?
>
> The main documentation for this is in the Worg page for ob-python, in
> particular see the section "Return values":
>
> https://orgmode.org/worg/org-cont
Hello,
I have been experimenting with org-cite. I noticed that I can insert
(org-cite-insert) all bibtex types *except* for @conference. For example:
@misc{foo123,
author = {joe},
title ={baba},
booktitle ={cacab},
year = 1999
}
works fine (and all other types t
The next code snippet makes the entry to appear in the agenda:
* sample date code
#+begin_src org
SCHEDULED: <2015-02-16 Mon .+2d>
#+end_src
I have also tried without success:
- using begin_example,
- preceding with comma,
- special edit,
- starting the line with colon.
Any hint?
On the other h
Ihor Radchenko writes:
> However, thinking about it more, I feel that prioritising underline
> should work better. The underline parser recently got changed into a
> stricter version. Now, only underlines starting after spaces,-,(,',",
> and { are recognised as an underlines.
>
> So, the attached
On Sat, Jan 1, 2022 at 9:31 AM Allen Li wrote:
> It seems like the right fix here is to make - behave the same as -1, and
> raise a user error for any other negative numeric prefix, since it is
> likely not doing whatever the user wanted.
>
Attached a small patch fixing this, which I tested manu
The docstring for org-todo (C-c C-t) is unclear about the handling of -
prefix compared to -1 prefix.
Here is the relevant part of the docstring:
With ‘C-u’ prefix ARG, force logging the state change and take a
logging note.
With a ‘C-u C-u’ prefix, switch to the next set of TODO keyw
16 matches
Mail list logo