[no subject]

Sébastien Gendre writes: > When I try to execute a block of PlantUML in an Org document, I get an > error message: > > "org-babel-execute-src-block: No org-babel-execute function for plantuml!" > ... > (add-to-list > 'org-babel-load-languages > '(plantuml . t)) Just use (require

[no subject]

Hello, When I try to execute a block of PlantUML in an Org document, I get an error message: "org-babel-execute-src-block: No org-babel-execute function for plantuml!" I have configured Org mode to enable execution of plantUML source block by adding this in my init.el: (setq

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Thanks Alan, I found a fix to my problem. -- Nasser Alkmim +43 677 6408 9171

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Hello, On 2024-03-17 19:05, Nasser Alkmim writes: > Hi Alan, how did you effectively solve the problem? Here is the contents of my export-init file: (setq user-emacs-directory "/Users/schmitta/projets/plain-emacs-config/") (add-to-list 'load-path (expand-file-name "straight/build/org/"

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Alan Schmitt writes: > > The document header was not the problem, as it happened with any > file. The core of the issue is that the org version used to initiate the > export must be the same than the org version run in the asynchronous > export process, as bytecode from org is passed between

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Alan Schmitt writes: > > The document header was not the problem, as it happened with any > file. The core of the issue is that the org version used to initiate the > export must be the same than the org version run in the asynchronous > export process, as bytecode from org is passed between

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Hi Pedro, On 2024-03-08 18:07, Pedro Andres Aranda Gutierrez writes: > I’m very interested on how your document header looks like. Can you please > send mee a file with your header > and a couple of dummy slides? I’m not able to reproduce the problem… The document header was not the problem,

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Hi, I’m very interested on how your document header looks like. Can you please send mee a file with your header and a couple of dummy slides? I’m not able to reproduce the problem… Thx, /PA > El 7 mar 2024, a las 10:42, Alan Schmitt > escribió: > > Hi Pedro, > > On 2024-03-07 10:03, Pedro

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Will try with my setup @home with the main branch of the git to check again. /PA Enviado desde mi iPhone > El 7 mar 2024, a las 10:42, Alan Schmitt > escribió: > > Hi Pedro, > > On 2024-03-07 10:03, Pedro Andres Aranda Gutierrez writes: > >> could you please try to add >> >>

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Hi Pedro, On 2024-03-07 10:03, Pedro Andres Aranda Gutierrez writes: > could you please try to add > > #+LATEX_CLASS: beamer > #+LATEX_CLASS_OPTIONS: [presentation,aspectratio=169] > > instead of > > (require 'ox-latex) > > (add-to-list 'org-latex-classes > '("my-beamer" >

Re: Subject: cannot export asynchronously because of org-fold-core--update-buffer-folds

Hi, could you please try to add #+LATEX_CLASS: beamer #+LATEX_CLASS_OPTIONS: [presentation,aspectratio=169] instead of (require 'ox-latex) (add-to-list 'org-latex-classes '("my-beamer" "\\documentclass\[presentation,aspectratio=169\]\{beamer\}

Re: [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix

Ihor Radchenko writes: > Bastien writes: > >> Adding [BLOG] or [TIP] in the subject prefix allows for such messages >> to be referenced on https://tracker.orgmode.org/news (along with [ANN] >> messages). >> >> It will then be possible to include these

Re: [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix

Bastien writes: > Adding [BLOG] or [TIP] in the subject prefix allows for such messages > to be referenced on https://tracker.orgmode.org/news (along with [ANN] > messages). > > It will then be possible to include these posts in the orgmode.org > homepage, using e.g. https://t

Re: emacs-orgmode@gnu.org Subject: Org mode version 9.7-pre (9.7-pre-n/a-g356072; org-table-to-lisp breaks table alignment when using links

Kostadin Ninev writes: > After installing latest org from git, table alignment is broken for > me in tables where some of the cells contain links for example: > > > | a| b | > |--+---| > | [[c][c]] | d | > > > Shows like this: > > > | a| b | > |--+---| > | c | d

emacs-orgmode@gnu.org Subject: Org mode version 9.7-pre (9.7-pre-n/a-g356072; org-table-to-lisp breaks table alignment when using links

After installing latest org from git, table alignment is broken for me in tables where some of the cells contain links for example: | a| b | |--+---| | [[c][c]] | d | Shows like this: | a| b | |--+---| | c | d | Unless I M-x org-toggle-link-display, tested

Re: [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix

> Yes, you can use "[BLOG] [Spanish] ..." so that people adapt their > filters, but the second prefix won't have any effect on Woof. If we want to add a hint about the blog post language, can I suggest using the two-letter ISO-639 language codes (SP, DE, IT, EN, ...)? I agree they don't cover

Re: [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix

Ihor Radchenko writes: > As long as the fraction of non-English posts is small, I do not think > that it matters too much. (Of course, having a translation would be > helpful, but we cannot demand such thing.) I suggest we stick to the policy of using english as the language for the list:

Re: [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix

Hi Juan, Juan Manuel Macías writes: > Great! Just one question: can articles be shared in languages other than > English? In that case, would it be necessary to add some more > prefixes, such as "Spanish", "French", "Italian", "Greek", etc.? Yes, you can use "[BLOG] [Spanish] ..." so that

Re: [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix

Juan Manuel Macías writes: > Great! Just one question: can articles be shared in languages other than > English? In that case, would it be necessary to add some more > prefixes, such as "Spanish", "French", "Italian", "Greek", etc.? > > (If I shared something in Spanish, I could translate the

Re: [ANN] Please share useful blog posts on this list with the [BLOG] subject prefix

Bastien writes: > Adding [BLOG] or [TIP] in the subject prefix allows for such messages > to be referenced on https://tracker.orgmode.org/news (along with [ANN] > messages). > > It will then be possible to include these posts in the orgmode.org > homepage, using e.g. https://t

[ANN] Please share useful blog posts on this list with the [BLOG] subject prefix

Adding [BLOG] or [TIP] in the subject prefix allows for such messages to be referenced on https://tracker.orgmode.org/news (along with [ANN] messages). It will then be possible to include these posts in the orgmode.org homepage, using e.g. https://tracker.orgmode.org/news.rss

[no subject]

Forgive for the noise, I just double checked the patch and noticed the `current-prefix-arg' was still being used. Fixed.

[no subject]

I was playing with your file and changed the last block: #+begin_src emacs-lisp :var alist=animal_list() (mapcar #'(lambda (x) (message "mapcar %s" x)) alist) #+end_src #+RESULTS: | mapcar 10 | mapcar 34 | mapcar 103 | mapcar 97 | mapcar 122 | mapcar 101 | mapcar 108 | mapcar 108 | mapcar 101 |

Re: This is out of thread subject

Jean Louis writes: >> Well... >> https://bugzilla.mozilla.org/show_bug.cgi?id=1678994 > > That is fine, it is useful to be asked by which application something > will be opened. It is question about permission, which is given > once. That does not prevent user opening any URL with external >

Re: This is out of thread subject

* Ihor Radchenko [2023-01-25 21:01]: > Jean Louis writes: > > > Haven thanks Firefox developers did not complain on users setting > > their own content types. Firefox can open Org content type and launch > > Emacs on it, but Emacs "can't" as it is security risk. > > Well... >

Re: This is out of thread subject

Jean Louis writes: > Haven thanks Firefox developers did not complain on users setting > their own content types. Firefox can open Org content type and launch > Emacs on it, but Emacs "can't" as it is security risk. Well... https://bugzilla.mozilla.org/show_bug.cgi?id=1678994

This is out of thread subject

* Max Nikulin [2023-01-25 18:33]: > I had in mind another person: > > Re: URLs with brackets not recognised. Wed, 12 May 2021 22:06:50 +0200. > > I disagree. URLs are well-specified. Per RFC 3986, the characters > > allowed in a URL are [A-Za-z0-9\-._~!$&'()*+,;=:@\/?]. Org mode should > >

[no subject]

> I am unable to reproduce on my side using the latest main branch. > Can you please provide detailed steps you performed to get the erroneous > behaviour? See https://orgmode.org/manual/Feedback.html I'm very sorry for wasting your time, it looks like I had org-capture-after-finalize-hook

[no subject]

To: emacs-orgmode@gnu.org Subject: Bug: org-html-example-block can produce multiple class attributes [9.4 (9.4-dist @ /usr/share/emacs/site-lisp/elpa/org-9.4/)] From: Joshua Honeycutt --text follows this line-- Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

Hi lhor, You're totally right, the commit b5f0efc had appended the `-headless` to the jar parameter list. Here is the comment: > *** =org-plantump-executable-args= is renamed and applies to jar as well The original issue does not exist now. Please ignore the previous patch. Thank you so much.

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

lin Sun writes: > The commit f9dcc3d was overridden by the commit b5f0efc. > > This patch will re-submit the solution based on the last rev. > > Please help review and merge the patch. Thanks I am unable to reproduce the original error on latest main. Could you please provide a reproducer when

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

On 07/06/2022 13:34, Dr. Arne Babenhauserheide wrote: lin Sun writes: This patch will re-submit the solution based on the last rev. diff --git a/lisp/ob-plantuml.el b/lisp/ob-plantuml.el index 6e1b1b1..37a631b 100644 --- a/lisp/ob-plantuml.el +++ b/lisp/ob-plantuml.el @@ -122,6 +122,7 @@

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

html-export.patch]... > From 6512e94806a4c08f40e6796e239ad2b318f7fbc5 Mon Sep 17 00:00:00 2001 > From: Lin Sun > Date: Tue, 7 Jun 2022 04:06:06 + > Subject: [PATCH] ob-plantuml: fix DISPLAY error with html export > > * lisp/ob-plantuml.el (org-babel-execute:plantuml): Use headless mode &g

Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

04:06:06 + Subject: [PATCH] ob-plantuml: fix DISPLAY error with html export * lisp/ob-plantuml.el (org-babel-execute:plantuml): Use headless mode for Org calling plantuml for exporting to html to avoid issues with operations that normally try to access the system graphics stack. --- lisp/ob

Re: org-capture problems again, the evil %from, %subject

Uwe Brauer writes: > I am again facing the problem that org-capture hangs even with my > recovered old setting. > > I investigated it a bit, org-capture is mostly ok, but not for those > templates that contain gnus specific commands like %from %subject etc > > How can I

org-capture problems again, the evil %from, %subject

Hi I am again facing the problem that org-capture hangs even with my recovered old setting. I investigated it a bit, org-capture is mostly ok, but not for those templates that contain gnus specific commands like %from %subject etc How can I debug this? Regards Uwe Brauer -- I strongly

[no subject]

Hello, I want to run stack ghci from haskell blocks in org-mode. For the task at I need to start ghci with command line option -XFlexibleContexts. I have this in my org-mode buffer: #+begin_src emacs-lisp :results none (setq haskell-process-type 'stack-ghci) (setq

Subject: Re: [patch] improved: add TTL as defcustom to ox-icalendar

essage: 9 > Date: Mon, 3 Jan 2022 08:41:41 +0100 > From: Detlef Steuer > To: emacs-orgmode@gnu.org > Subject: Re: [patch] improved: add TTL as defcustom to ox-icalendar > Message-ID: <20220103084141.72d2f...@hsu-hh.de> > Content-Type: text/plain; charset="us-ascii"

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

Hi Timothy, Thank you! : )  I had signed the FSF, RT: 1718442.  B.R.  Lin On Tuesday, November 30, 2021, 04:22:03 AM UTC, Timothy wrote: > Hi Sun, > Thanks for not forgetting about this. As I commented before, I this looks  sensible enough to apply, and so I’ve just pushed it as f9dcc3d

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

Hi Sun, > Can any help merge the patch? Or should I request Bastien to merge the patch?  Thanks for not forgetting about this. As I commented before, I this looks sensible enough to apply, and so I’ve just pushed it as f9dcc3d with a tweaked commit message. You’ve also been added to the list of

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

Hi Sun, > [snipped patch description] > Please help review the patch. Thanks. > [2. text/x-patch; > 0001-Fix-DISPLAY-error-on-exporting-org-with-plantuml-to-.patch]... Thanks for your patience. This looks quite straight-forward. I don't use or have plantuml so I'm in a poor position to test.

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

Hi Timothy, Thank you so much! B.R. Lin

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

anks. Lin    From 5e04a800691b04edd940dd124987336f6f30dd62 Mon Sep 17 00:00:00 2001 From: Lin Sun Date: Sat, 16 Oct 2021 03:01:18 + Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html * org-babel-execute:plantuml: using headless mode for org calling plantuml for exporting to html --- lisp/ob-plantum

Re: Subject: [BUG] error when visit bibtex file link [9.5 (9.5-gd4e192 @ c:/Users/scott/.emacs.d/straight/build/org/)]

Scott Otterson writes: > When I type C-c o on a bibtex file link like this: > > [[file:energy.bib::Dubitzky07datMinGenBook][Dubitzky et al. 2007: > Fundamentals]] > > I get the error message shown below: > > === *Warnings* > > Warning (emacs):

Re: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

Hi, Sun Lin writes: > Please help to review this patch. I will - but please be aware that we have a policy of waiting at least one month before bumping a thread: https://orgmode.org/worg/org-mailing-list.html#i-didnt-receive-an-answer Thanks, -- Bastien

Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html

Hi Bastien, Please help to review this patch. Thanks Best Regards Lin Sun - Forwarded Message - From: Sun Lin To: emacs-orgmode@gnu.org Sent: Saturday, October 16, 2021, 03:25:40 AM UTC Subject: Subject: [PATCH] Fix DISPLAY error on exporting org with plantuml to html Hi, When

Re: [PATCH] Re: Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

Hi Ihor, Ihor Radchenko writes: > Eddie Drury writes: > >> I have followed those steps and that is the same behaviour I get. >> >> The expected behaviour is for it to clock out of the subtree, instead of >> giving the "Clock start time is gone" error. > > I can also reproduce. The fix is

[PATCH] Re: Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

ed. Best, Ihor >From 4ad92b3efc8717e3ca871ab83bcb5e23e8faeb35 Mon Sep 17 00:00:00 2001 Message-Id: <4ad92b3efc8717e3ca871ab83bcb5e23e8faeb35.1627654962.git.yanta...@gmail.com> From: Ihor Radchenko Date: Fri, 30 Jul 2021 22:16:02 +0800 Subject: [PATCH] Fix not updating org-clock-marker after refiling from

Re: Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

Hi Bhavin, Thanks for your prompt response. I have followed those steps and that is the same behaviour I get. The expected behaviour is for it to clock out of the subtree, instead of giving the "Clock start time is gone" error. Regards, - Eddie Drury On Wed, 21 Jul 2021 at 02:00, Bhavin

Re: Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

Hello Eddie On Mon, 19 Jul 2021 at 16:15, Eddie Drury wrote: > > When I am working in an indirect buffer and am currently clocked into a > subheading. If I refile this subheading and then run org-clock-out, I get the > error "Clock start time is gone". I'm not sure if this is intended

Subject: Bug: Org-Clock-Out in indirect buffer error after refile [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.23, cairo version 1.16.0) of 2021-01-18, modified by Debian Package: Org mode version 9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/) Hi, When I am working in an indirect buffer and am currently clocked into a

[no subject]

Hi Bastien, I'm interested in taking 'charge' of maintenance of 'orgmode.org/worg'. My whole life revolves around org files. I use it extensively for personal knowledge management, appointments, lessons, project management using TaskJuggler, Python development using literate-programming, private

[no subject]

leave

[no subject]

Hello, all. I would like to contribute this tweak that I have been using in my personal config (though in the form of advice). As with Python, in Ruby there is significant need to be able to specify the Ruby command invoked. For instance when managing dependencies with Bundler (which is very

Re: Bug: A tag of a subject doesn't get archived if org-archive-subtree-add-inherited-tags t [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.3/lisp/org/)]

Hi, hpgislero...@bluewin.ch writes: > a) > if: org-archive-subtree-add-inherited-tags nil > then: Archiving a subject with its tag (C-c $) works as expected, > i.e. the subject together with it's tag is archived > b) > if: org-archive-subtree-add-inherited-tags t

Bug: A tag of a subject doesn't get archived if org-archive-subtree-add-inherited-tags t [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.3/lisp/org/)]

a) if: org-archive-subtree-add-inherited-tags nil then: Archiving a subject with its tag (C-c $) works as expected, i.e. the subject together with it's tag is archived b) if: org-archive-subtree-add-inherited-tags t then Archiving a subject with its tag (C-c $) archives

Re: Subject: Bug: org-clock and indirect org buffer: unable to generate report with :scope file-with-archives [9.4 (nil @ /home/user/.emacs.d/.local/straight/build/org-mode/)]

I apologize that I got to this so late, I tested it and it works, issue is fixed, with, I must say, nice and systematic approach. Thank you. On Sat, May 16, 2020 at 8:44 PM Nicolas Goaziou wrote: > > Hello, > > Alois Janíček writes: > > > When attempting to generate clock-report using ":scope

bug#24198: bug#24211: Subject: 25.0.94; Proposal to make orgmode agenda really useful

Hi Christoph, thanks for the proposal about enhancing Org Agenda. If you think it is still useful to push for this idea, can you repost it to emacs-orgmode@gnu.org, where such feature requests are discuted, preferrably with one feature per thread? I am closing the report from here. Thanks, --

Re: Subject: Bug: org-clock and indirect org buffer: unable to generate report with :scope file-with-archives [9.4 (nil @ /home/user/.emacs.d/.local/straight/build/org-mode/)]

Hello, Alois Janíček writes: > When attempting to generate clock-report using ":scope > file-with-archives" from indirect org buffer, operation fails because > function `org-dblock-write:clocktable` builds list of files based on > `buffer-file-name` variable which is `nil` in indirect buffers.

Subject: Bug: org-clock and indirect org buffer: unable to generate report with :scope file-with-archives [9.4 (nil @ /home/user/.emacs.d/.local/straight/build/org-mode/)]

When attempting to generate clock-report using ":scope file-with-archives" from indirect org buffer, operation fails because function `org-dblock-write:clocktable` builds list of files based on `buffer-file-name` variable which is `nil` in indirect buffers. As user I am expecting org-clock to

Re: Subject: [PATCH] org-id: Allow file name to be overridden on ID creation

Kyle Meyer writes: > Subject: [PATCH] org-id: Allow file name to be overridden on ID creation Applied (c716b7c08).

Subject: [PATCH] org-id: Allow file name to be overridden on ID creation

h is that the IDs of > cloned subtrees won’t be tracked correctly. That sounds right, so it seems it was just broken in a quieter way before. > Perhaps a solution to that is to use an indirect buffer of the source > when cloning, instead of a temp buffer. Hmm, that should indeed work, bu

[no subject]

Subject: [PATCH] ox-html: escape & in license magnets In-Reply-To: <87d09dz92a@yandex.com> Date: Sun, 15 Mar 2020 23:36:37 +0100 References: <87eett7bql@yandex.com> <871rpt9zc4@kyleam.com> <87d09dz92a@yandex.com> References: <87d09dz92a@yan

problem with org-toggle-inline-images - SORRY - WRONG SUBJECT

Hi! Frequently I publish org-mode documents containing source code blocks to html (htmlize) and pdf (minted). I would like to see the same colors in both export types. But I cannot figure out, what’s the best way to achieve this. Has anyone solved this problem? Are there any hints? Johannes

Re: change to mail-list subject line?

not sure if that works in gmail, however. maybe it's possible to add an "o" tag [or whatever gmail calls it], but i'm not sure if there is a complete and reliable header parser. On 10/31/19, adam wrote: > > Thanks.  Just found that now. > > > > > -- The Kafka Pandemic What is misopathy?

Re: change to mail-list subject line?

Thanks.  Just found that now. 

Re: change to mail-list subject line?

On 30/10/2019 23:03, adam wrote: > > Has the emacs-orgmode  mail-list ceased including a  [O]  in the subject  > line of its mails?  Or, what has changed here? Yes, as announced on the list a couple of days ago. > I was using  [O]  as a filter for my incoming mails, now they are 

change to mail-list subject line?

Has the emacs-orgmode  mail-list ceased including a  [O]  in the subject  line of its mails?  Or, what has changed here?  I was using  [O]  as a filter for my incoming mails, now they are  turning up unsorted amongst my general mail.   OK. I can filter on and   Sorry for the noise.   Any

Fyi: this list, emacs-orgmode, just had it's subject [tag] and footer removed

The Free Software Foundation has changed the GNU Mailman settings on this list. The short version is that any subject prefix or message footer has been removed, allowing us to turn off DMARC from munging. Any list administrator for this list is free to change these settings back, instructions

Re: [O] (no subject)

I'm replying a year late to this thread, post-merge, because I've discovered it breaks interaction with the highlight.js library( https://highlightjs.org/) and therefore my workflow, which depends on highlightjs via reveal.js. My difficulty is with the current version of

[no subject]

A_NEGATE 0, __SUBJ_REPLY 0, __TO_MALFORMED_2 0, __TO_NAME 0, __TO_NAME_DIFF_FROM_ACC 0, __TO_REAL_NAMES 0, __URI_NO_WWW 0, __URI_NS ' X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 140.142.234.175 Subject: Re: [O] org-agenda fails when a

[no subject]

95.242.222 Subject: Re: [O] org-agenda fails when a scheduled/deadline date is in the past [9.1.9 (release_9.1.9-65-g5e4542 @ /Users/borwick/.emacs.d/elpa/org-plus-contrib-20190218/)] X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "General discussions

[no subject]

S_NXDOMAIN , __URI_WITH_PATH 0' X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 128.95.242.222 X-Mailman-Approved-At: Tue, 19 Feb 2019 14:27:39 -0500 Subject: [O] Bug: org-agenda fails when a scheduled/deadline date is in the past [9.1.9 (release_9.1.9-65-g5e4542

[O] (no subject)

At the bottom of this is a description of adding a `org-store-link` inside of a babel code block edit called with C-c ' , however, it doesn't seem to work with C-c l , although M-x org-store-line does work. Or am I seeing, doing this wrong? LB

Re: [O] org-store/insert-link truncating the full subject of mails

Hello, "Garreau, Alexandre" writes: > This is an argument in favor of immobility. True. Immobility is sometimes good, too. > Yes, if only each user of each piece of software took the time to read > the integrality of documentation each time they used something: I don’t > and only did

Re: [O] org-store/insert-link truncating the full subject of mails

y or the other: most of the time, I just want to save the email for some information that it contains which may or may not be related to the subject line. So I have a capture template that saves the link, but I add my description of *why* I'm saving the email (and add tags too), so I have a chance of

Re: [O] org-store/insert-link truncating the full subject of mails

On Friday, 26 Oct 2018 at 21:54, Nicolas Goaziou wrote: [...] > In any case, if other users feel strongly about changing the default > value, I don't mind. I hope you understand that one data point is not > enough, tho. Just to add a data point: I've been annoyed by the default behaviour for

[O] org-email-link-description-format (Was: Re: org-store/insert-link truncating the full subject of mails)

er line limit, however Gnus already include this limitation in fill-column so that to fold subject line in several lines that will be no more than 78 characters, there’s no need to limit to 78 characters, and indeed I sometimes end with subject lines of more than one line, and wouldn’t like to

Re: [O] org-store/insert-link truncating the full subject of mails

t; That somehow feels less arbitrary, and would cover a larger > portion of subjects. Rather cutting it, I’d rather try to find the gnus function that cut subject lines so it does more semantically (like, removing the entire Was: part if it doesn’t fit, rather than cutting it in the middle), but

Re: [O] org-store/insert-link truncating the full subject of mails

Hi, Nicolas Goaziou writes: > I don't know. This is why I agree it is safer to limit length to an > arbitrary number instead of allowing any size. Hoping to find an actual answer, I did a =git blame lisp/org.el= and found the commit that introduced it, 2c16f092e64915a7e3d0b2dda82f3978a0f42dea,

Re: [O] org-store/insert-link truncating the full subject of mails

. What could be done, if you want, is to rely on external software: for instance, sometimes, when answering, Gnus takes away the “Was: ...” subject line ending, if too long: that might be used to shorten it, if believed useful. That would be acceptable, as it would stay semantic, and wouldn’t break in

Re: [O] org-store/insert-link truncating the full subject of mails

. What could be done, if you want, is to rely on external software: for instance, sometimes, when answering, Gnus takes away the “Was: ...” subject line ending, if too long: that might be used to shorten it, if believed useful. That would be acceptable, as it would stay semantic, and wouldn’t break in

Re: [O] org-store/insert-link truncating the full subject of mails

"Garreau, Alexandre" writes: > Without justification, that’d look like “argument from ignorance”, I'm not arguing for truncating subjects. However, I'm arguing against changing a 10 years old default value without a strong reason. Default value annoys some users. Point taken. But changing it

Re: [O] org-store/insert-link truncating the full subject of mails

Le 27/10/2018 à 11h27, Nicolas Goaziou a écrit : > Hello, > > Amin Bandali writes: > >> Can you please elaborate on what you mean by being on the safe >> side in this context? What problems could potentially arise from >> returning the subject in full length? &

Re: [O] org-store/insert-link truncating the full subject of mails

Hello, Amin Bandali writes: > Can you please elaborate on what you mean by being on the safe > side in this context? What problems could potentially arise from > returning the subject in full length? I don't know. This is why I agree it is safer to limit length to an arbitrary numbe

Re: [O] org-store/insert-link truncating the full subject of mails

ems could potentially arise from returning the subject in full length? > In any case, if other users feel strongly about changing the default > value, I don't mind. I hope you understand that one data point is not > enough, tho. Considering my above question and me not knowing why/wher

Re: [O] org-store/insert-link truncating the full subject of mails

"Garreau, Alexandre" writes: > How’s that? I think limiting the number of characters in the description is to be on the safe side. 30 characters are usually enough to understand what the mail is about. > it just feels wrong: if it’s to long, users can truncate themselves, > it’s

Re: [O] org-store/insert-link truncating the full subject of mails

Hello, "Garreau, Alexandre" writes: > Why so? See `org-email-link-description-format'. > It shouldn’t be this way by default. Truncating subject doesn't seem unreasonable to me. In any case, you can just set the variable above to suit your needs. Regards, -- Nicolas Goaziou

Re: [O] org-store/insert-link truncating the full subject of mails

Le 26/10/2018 à 17h35, Nicolas Goaziou a écrit : > "Garreau, Alexandre" writes: >> Why so? > > See `org-email-link-description-format'. Thank you! >> It shouldn’t be this way by default. > > Truncating subject doesn't seem unreasonable to me. In any case,

[O] org-store/insert-link truncating the full subject of mails

Why so? It shouldn’t be this way by default. I tried to link “[[gnus:nnml:lists.gnu.emacs-orgmode#87in1rkqlk@gmail.com][Email from Tim Cross: Re: {O} Ox-html: Replace with and with ]]” and after org-store-link in appropriated buffer, org-insert-link gave me “Email from Tim Cross: Re: {O}

[O] (no subject)

Org source block header argument :var does not support quoted string with space separator like bellowing example: For example encrypt text -- ~<<< [TEXT]~ #+NAME: base64 encrypt text #+begin_src sh base64 <<< "stardiviner " #+end_src #+RESULTS: base64 encrypt text :

Re: [O] (no subject)

Hello, Nik Clayton writes: > I'd like to propose a couple of changes / enhancements to how org-export > exports some data in to HTML files to make it slightly easier to style > those files. > > The first is re line-numbers. [...] > Couple of questions before I write a patch: > > a) Does that

[O] (no subject)

Hi, I'd like to propose a couple of changes / enhancements to how org-export exports some data in to HTML files to make it slightly easier to style those files. The first is re line-numbers. At the moment those get exported as content in the HTML, although they're really additional metadata.

Re: [O] Subject: Bug: Confusing documentation for org-complete-tags-always-offer-all-agenda-tags [9.1.14 (9.1.14-1-g4931fc-elpaplus @ /home/n/.emacs.d/elpa/org-plus-contrib-20180917/)]

Hello, > That aside, the wording of the second sentence could be clearer. > My humble suggestion: > > "If non-nil, always offer completion for all tags of all agenda files. > Setting this variable locally allows for dynamic generation of tag > completions in capture buffers." Applied. Thank you.

[O] Subject: Bug: Confusing documentation for org-complete-tags-always-offer-all-agenda-tags [9.1.14 (9.1.14-1-g4931fc-elpaplus @ /home/n/.emacs.d/elpa/org-plus-contrib-20180917/)]

The documentation for org-complete-tags-always-offer-all-agenda-tags currently reads: "If non-nil, always offer completion for all tags of all agenda files. Instead of customizing this variable directly, you might want to set it locally for capture buffers, because there no list of tags in that

Re: [O] (no subject)

Hello, "Arne Babenhauserheide" writes: > Dear Org Hackers, > > When I use org-capture to capture a new task, the next headline > sometimes ends up being prefixed by the last line of the new task. > > Example: > > Begin: > > * Foo > ** old task > > * Bar > > After capture: > > *

Re: [O] (no subject)

Hello, Bastien writes: > Dear Arne, > > there was a temporary glitch in earlier version of Org about this, > please upgrade Org to 9.1.12 through the package system and let us > know if you still have this issue. oh, i thought that is a feature of some kind. Let me upgrade... Hm,

Re: [O] (no subject)

FYI I am on org 9.1.4 and am still seeing this issue. -- Steen On Thu, May 3, 2018 at 2:26 PM Arne Babenhauserheide <arne_...@web.de> wrote: > Dear Bastien, > > Thank you for your answer! I’ll check whether the update resolves this. > > > (and I’m sorry for the

Re: [O] (no subject)

Dear Bastien, Thank you for your answer! I’ll check whether the update resolves this. (and I’m sorry for the empty subject, I copied the email from Emacs, since I do not have mail sending from emacs configured at work, and I forgot to copy the subject). Best wishes, Arne Bastien <b...@gnu.

Re: [O] (no subject)

Dear Arne, there was a temporary glitch in earlier version of Org about this, please upgrade Org to 9.1.12 through the package system and let us know if you still have this issue. Thanks! -- Bastien

  1   2   3   4   >