Re: [PATCH] lisp/org-agenda.el: Fix filter preset problem for sticky agenda

! > Also, while we are at it, may you take a look at > https://list.orgmode.org/paxpr06mb7760f3a02d140e7de2baaec6c6...@paxpr06mb7760.eurprd06.prod.outlook.com/? > AFAIR, it is caused by a similar symbol property approach employed in > different place in org-agenda.el. The issue seems

Re: [PATCH] lisp/org-agenda.el: Fix filter preset problem for sticky agenda

ty. > > From 718cb5258a407d8a51eb4a5bac3d0c8025a3f198 Mon Sep 17 00:00:00 2001 > From: Liu Hui > Date: Tue, 4 Oct 2022 11:12:41 +0800 > Subject: [PATCH] Fix filter preset problem for sticky agenda Applied onto main with minor amendments (mostly added double space " " between s

Re: [PATCH] lisp/org-agenda.el: Fix filter preset problem for sticky agenda

w the udpated patch can address the case containing one command by changing another global symbol property to per-buffer text property. >From 718cb5258a407d8a51eb4a5bac3d0c8025a3f198 Mon Sep 17 00:00:00 2001 From: Liu Hui Date: Tue, 4 Oct 2022 11:12:41 +0800 Subject: [PATCH] Fix filter p

Re: [PATCH] lisp/org-agenda.el: Fix filter preset problem for sticky agenda

Hi Ihor and Liu, Ihor Radchenko writes: >> I have signed the FSF >> copyright assignment paper. > > Bastien, could you please confirm the FSF records? I do confirm, I updated https://orgmode.org/worg/contributors.html Liu, thanks in advance for contributing to Org! Best, -- Bastien

Re: [PATCH] lisp/org-agenda.el: Fix filter preset problem for sticky agenda

recipe. The bug still exists in latest > org-mode. > ... > > Because the filter presets are stored as symbol properties, they > cannot be used with multiple sticky agenda buffers. The patch fixes > the problem by adding a new variable `org-agenda-filters-preset' for > getting a

[PATCH] lisp/org-agenda.el: Fix filter preset problem for sticky agenda

.org > > Followed by: > > C-c a f > C-c a b > C-x o > r > > I would expect pressing `r' in the `*Org Agenda(f)*' buffer would > keep the original `org-agenda-category-filter-preset' and that the > preset in `*Org Agenda(b)*' should have no bearing on it. But, as yo

Re: [BUG] Server-side export problem in Worg?

Thank you for the fix! Joseph Bastien Guerry writes: > Ihor Radchenko writes: > >> Bastien, there seems to be an issue with Worg export on server. Can you >> please check? > > This is now fixed, thanks: > > https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html#org6cd541e

Re: [BUG] Server-side export problem in Worg?

Ihor Radchenko writes: > Bastien, there seems to be an issue with Worg export on server. Can you > please check? This is now fixed, thanks: https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html#org6cd541e -- Bastien

Re: [BUG] Server-side export problem in Worg? (was: [PATCH] org-contrib/babel/languages/ob-doc-plantuml.org: ASCII output)

On 22/09/2022 19:18, Ihor Radchenko wrote: Joseph Turner writes: Actually, I just looked at the org-mode documentation on the site today, and noticed that the examples of use section (https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html#org6cd541e) has the wrong ASCII

[BUG] Server-side export problem in Worg? (was: [PATCH] org-contrib/babel/languages/ob-doc-plantuml.org: ASCII output)

Joseph Turner writes: > Actually, I just looked at the org-mode documentation on the site today, > and noticed that the examples of use section > (https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html#org6cd541e) > has the wrong ASCII output. The output should be > >

Re: Problem with installation

anilomjf writes: > Shoud org-version be in the lisp directory when I clone the repository? > > It is not. org-version.el should be generated by make script. Best, Ihor

Re: Problem with installation

[ Adding the org mailing list back to the CC ] anilomjf writes: > Here: > > https://orgmode.org/worg/org-faq.html#keeping-current-with-Org-mode-development > > > > It is stated that: > > Yes. You can install org-latest.zip or >

Re: Problem with installation

[ Adding the org mailing list back to the CC ] anilomjf writes: > Thank you for your rapid response. > > My emacs version is 27.1 I tested using Emacs 27.2 on Gentoo Linux using your exact steps. Still unable to reproduce. Best, Ihor

Re: Problem with installation

anilomjf writes: > Hi, > > I execute in kubuntu 22.04: > >> git clone https://git.savannah.gnu.org/git/emacs/org-mode.git >> cd org-mode >> make autoloads > > and get the messages: > ... > Loading /home/javi/org-mode/lisp/org-compat.el (source)... > Eager macro-expansion failure: (file-missing

Problem with installation

Hi, I execute in kubuntu 22.04: > git clone https://git.savannah.gnu.org/git/emacs/org-mode.git > cd org-mode > make autoloads and get the messages: == = Invoke "make help" for a synopsis of make targets. = = Created a default local.mk

Re: Bug: Folding problem with markdown source block

Jack Kamm writes: > I found that Org entries containing markdown source blocks don't get > properly folded on the main development branch, when markdown-mode is > also loaded. > > To reproduce: > > 1. Download markdown-mode from MELPA or Github. [1] > 2. Fix the paths in the attached init.el. >

Re: Bug: Folding problem with markdown source block

; > * Headline 1... > > But instead I observe this: > > * Headline 1... ``` > ... ``` > ... > > If markdown-mode isn't loaded, then the problem goes away. I think the > problem might have to do with the fontification that markdown-mode > applies to the back-quoted code block.

Bug: Folding problem with markdown source block

test.org 4. Shift-tab to collapse the visibility Output should look like this: * Headline 1... But instead I observe this: * Headline 1... ``` ... ``` ... If markdown-mode isn't loaded, then the problem goes away. I think the problem might have to do with the fontification that markdown-mode applies

[restarting helps, memory problem?] (was: [Problem persits])

>>> "UB" == Uwe Brauer writes: >>> "UB" == Uwe Brauer writes: >>> "UB" == Uwe Brauer writes: >>> Hi >>> I attach a file that hopefully explains the problem. >>> That file contains 109 heading, each headi

[Problem persits] (was: [a kludge])

>>> "UB" == Uwe Brauer writes: >>> "UB" == Uwe Brauer writes: >> Hi >> I attach a file that hopefully explains the problem. >> That file contains 109 heading, each heading has 17 different >> properties when all of them are includ

Re: Problem with defining stuck projects

On 22-07-08 12:51, Ihor Radchenko wrote: > "^[ \t]*\\(SCHEDULED:\\|DEADLINE:\\)" Ihor, This seems to work. Thank you. Regards, Bob

Re: Problem with defining stuck projects

Bob Heffernan writes: > I want the following: > 1. A project is a level 1 header marked as TODO > 2. A project is not stuck if it has any sub-header that is scheduled but > not closed. > > So, in the example above Project 1 counts as stuck, but Project 2 does not. > > What I've got so far

Problem with defining stuck projects

Dear all, I am having trouble setting org-stuck-projects in a way that works for me. My org-files are organised something like this... * Non-project header - blah, blah ** Foo * TODO Project 1 ** TODO Do this CLOSED: [2022-07-06 Wed 17:10] SCHEDULED: <2022-07-06 Wed> ** TODO Do

Re: How to debug a CSL problem

Hi Andras, I will do that. Thanks to all of you for your help and for the great system. I cannot believe that I once wrote using word processors!! Cheers, Alan On Mon, 6 Jun 2022 at 15:34, András Simonyi wrote: > Dear All, > > On Mon, 6 Jun 2022 at 03:45, Alan Tyree wrote: > > > A short random

Re: How to debug a CSL problem

Dear All, On Mon, 6 Jun 2022 at 03:45, Alan Tyree wrote: > A short random test shows that the export chokes when there is a single name > for an author. Again an example: > author = {{Wolfsberg Group}} works fine; > author = {{Wolfsberg}} chokes. Alan, could you open an issue in the

Re: How to debug a CSL problem

Thanks, Ihor. That found it. The bibtex entry had: author = {BIS}, Change to: author = {{Bank for International Settlements}}, and it all works a treat. A short random test shows that the export chokes when there is a single name for an author. Again an example: author = {{Wolfsberg Group}}

Re: How to debug a CSL problem

Alan Tyree writes: > I guess the bad news is that the csl file validates. I also should have > mentioned that everything parses properly with pandoc, so I guess it is a > cireproc-el glitch. > > From the brief error report, it must just be choking on a specific bibtex > entry, so it would still

Re: How to debug a CSL problem

uld still be helpful to be able to find it. Cheers, Alan On Mon, 6 Jun 2022 at 09:15, Bruce D'Arcus wrote: > On Sun, Jun 5, 2022 at 6:48 PM Alan Tyree wrote: > > > I need some help with a debugging problem: > > > > I'm using > > > > #+cite_export: csl ~/Temp

Re: How to debug a CSL problem

On Sun, Jun 5, 2022 at 6:48 PM Alan Tyree wrote: > I need some help with a debugging problem: > > I'm using > > #+cite_export: csl ~/Templates/csl/AGLC-intext.csl > > where AGLC-intext.csl is a custom csl file. I'm not sure if citeproc-el checks validity before running, b

How to debug a CSL problem

I need some help with a debugging problem: I'm using #+cite_export: csl ~/Templates/csl/AGLC-intext.csl where AGLC-intext.csl is a custom csl file. Exporting to html gives this error in *Messages*: citeproc-s-slice-by-matches: Wrong type argument: stringp, nil The error does not occur

Re: problem with unwanted strikeout in src blocks

>>> "JJ" == Jeremie Juste writes: > Hello Uwe >> On Monday, 23 May 2022 at 19:24, Uwe Brauer wrote: > Sorry I don't have matlab and I have never used the solutionorbox > environment, but I believe you can generate latex directly. For example > with R I can to the following. > #+begin_src R

Re: problem with unwanted strikeout in src blocks

>>> "IR" == Ihor Radchenko writes: > Uwe Brauer writes: >> However when I wrap a solutionorbox around it (which I need when >> exporting to latex) all text between the «+» >> gets a strikeout. >> >> >> #+begin_solutionorbox >> #+begin_src matlab :exports results :eval never-export :results

Re: problem with unwanted strikeout in src blocks

Uwe Brauer writes: > However when I wrap a solutionorbox around it (which I need when > exporting to latex) all text between the «+» > gets a strikeout. > > > #+begin_solutionorbox > #+begin_src matlab :exports results :eval never-export :results output latex >

Re: problem with unwanted strikeout in src blocks

Hello Uwe > On Monday, 23 May 2022 at 19:24, Uwe Brauer wrote: Sorry I don't have matlab and I have never used the solutionorbox environment, but I believe you can generate latex directly. For example with R I can to the following. #+begin_src R :exports results :eval yes :results output

problem with unwanted strikeout in src blocks

Hi The following code block is nicely displayed #+begin_src matlab :exports results :eval never-export :results output latex

Re: a problem with lilypond babel fontification

"" writes: > I’m using emacs compiled from trunk as of today. This is my minimal file > for testing: > > > #+begin_src lilypond :file shalala.pdf > \clef bass {c d e f g a b c' b a g f e d c} > #+end_src > > #+begin_src lisp > (setq tralala mimimi) > #+end_src > > > If I open it using `emacs

a problem with lilypond babel fontification

I’m using emacs compiled from trunk as of today. This is my minimal file for testing: #+begin_src lilypond :file shalala.pdf \clef bass {c d e f g a b c' b a g f e d c} #+end_src #+begin_src lisp (setq tralala mimimi) #+end_src If I open it using `emacs -Q`, both blocks get

Re: Problem with org-babel and geiser

Rudolf Adamkovič writes: > P.S. > > We should add 'testing/lisp/test-ob-scheme.el' or it will break again > sooner or later. Can we make the Org test suite depend on Geiser and > Guile? Given that Org uses Geiser out of the box, I think we should. > What do you think? Sounds reasonable.

Re: problem with diary sexps

On Friday, 8 Apr 2022 at 10:59, Ihor Radchenko wrote: > Should be fixed now in f6813dbe. See Confirmed. Thank you! -- : Eric S Fraga, with org release_9.5.2-426-gf6813d in Emacs 29.0.50

Re: problem with diary sexps

Eric S Fraga writes: > On Tuesday, 5 Apr 2022 at 19:22, Ihor Radchenko wrote: >> More accurate error can be found after setting calendar-debug-sexp to t. >> I got the following backtrace clearly indicating lexical scope issue: > > Which makes sense. The diary code does use entry and date as

Re: problem with diary sexps

On 05/04/2022 18:22, Ihor Radchenko wrote: Christian Stuermer writes: And the problem is gone, after reverting (result (if calendar-debug-sexp (eval sexp t) (condition-case nil (eval sexp t) back to (result (if calendar-debug-sexp

Re: problem with diary sexps

On Tuesday, 5 Apr 2022 at 19:22, Ihor Radchenko wrote: > More accurate error can be found after setting calendar-debug-sexp to t. > I got the following backtrace clearly indicating lexical scope issue: Which makes sense. The diary code does use entry and date as global variables so really needs

Re: problem with diary sexps

Christian Stuermer writes: > And the problem is gone, after reverting > >(result (if calendar-debug-sexp (eval sexp t) > (condition-case nil > (eval sexp t) > > back to > >(result (if cal

Re: problem with diary sexps

On Tuesday, 5 Apr 2022 at 12:28, Christian Stuermer wrote: > I've had the same problem after updating org from git with entries like > The commit introducing it is > https://github.com/bzg/org-mode/commit/6d73cd34a07796c33f9435bfc8c9a19e67656c7a > > And the problem is gone,

Re: problem with diary sexps

error. I wonder if this has anything to do with the changes to the use of advice? Nothing else in the recent changes in the git log seem to be relevant. I've had the same problem after updating org from git with entries like %%(org-anniversary 2000 4 4) X is %d years old The commit intro

problem with diary sexps

Hello all, I updated org today and now get Bad sexp at line 461 in /home/ucecesf/s/notes/diary.org: (let ((entry ) (date '(4 19 2022))) (diary-float t 2 3)) for a line that looks like <%%(diary-float t 2 3)> This has been in my diary for a very long time with no error. I wonder if this

Re: Problem with org-babel and geiser

Zelphir Kaltstahl writes: Hi Zelphir, > Geiser seems to work, if I use /bin/sh with some arguments instead of > GNU Bash. I have no idea it means to "use /bin/sh with some arguments instead of GNU Bash" in the context of Org Babel, Geiser, and Guile. Then, please see my other mail, the reply

Re: Problem with org-babel and geiser

Neil Jerram writes: Hi Neil! > What do you see if you add ":results output" to the "#+begin_src" > line, and then C-c C-c again? #+BEGIN_SRC scheme :results output verbatim (+ 1 1) #+END_SRC #+RESULTS: : Geiser Interpreter produced no output > Did the patch help in your case? I had to

Re: Problem with org-babel and geiser

Hi Rudy, On Thu, 17 Mar 2022 at 17:07, Rudolf Adamkovič wrote: > > Bob Heffernan writes: > > > I did as you described and the patched version of ob-scheme.el *does* > > seem to solve the problem. > > Today, I needed to use Scheme with Org (9.5.2-24-g668205), and I

Re: Problem with org-babel and geiser

Hello Rudy! On 3/22/22 21:51, Rudolf Adamkovič wrote: Zelphir Kaltstahl writes: Hello Zelphir! At some point something changed, I think, […] In Geiser or in Org? I use Geiser for work heavily and it works like magic. I ask because if the problem resides in Geiser, we could report a new

Re: Re: Problem with org-babel and geiser

Zelphir Kaltstahl writes: Hello Zelphir! > At some point something changed, I think, […] In Geiser or in Org? I use Geiser for work heavily and it works like magic. I ask because if the problem resides in Geiser, we could report a new bug there. Rudy -- "One can begin to reason o

Re: Re: Problem with org-babel and geiser

Hello Rudy! On 3/18/22 17:00, emacs-orgmode-requ...@gnu.org wrote: Today, I needed to use Scheme with Org (9.5.2-24-g668205), and I found that the #+RESULTS: always come back empty. Oh, well! I use Guile and have everything configured correctly. Has anyone merged the patch discussed in this

Re: Problem with org-babel and geiser

Bob Heffernan writes: > I did as you described and the patched version of ob-scheme.el *does* > seem to solve the problem. Today, I needed to use Scheme with Org (9.5.2-24-g668205), and I found that the #+RESULTS: always come back empty. Oh, well! I use Guile and have everything conf

Re: [CLOSED] TEC fixed this problem.

Hi Christopher, "Christopher M. Miles" writes: > Today, I found the Org Agenda sorting strategy problem is fixed by > commit "1b675f0ca84d637a3780cf3590308116e232fcfd". thanks for confirming and thanks to TEC for fixing it! Best, -- Bastien

Re: Problem with org-babel and geiser

e sufficient to test the proposed patch on > your side. > > If the patch solves the problem you are experiencing, let us know. I > will then apply the proposed patch upstream. > > Note that even if I apply the patch, it will only be available on the > latest version of Org m

Re: Problem with org-babel and geiser

of ob-scheme.el. Load your Emacs and Org mode, open the attached ob-scheme.el, and run M-x eval-buffer. That should be sufficient to test the proposed patch on your side. If the patch solves the problem you are experiencing, let us know. I will then apply the proposed patch upstream. Note that even i

Re: Problem with org-babel and geiser

On 22-02-04 15:00, Ihor Radchenko wrote: > Does the patch in > https://orgmode.org/list/3462869.oopU1TnKvU@felipe-thinkpad-x200 help? Ihor, Thank you for your response. The patch you linked does seem to be intended to fix this issue. However, I have no experience with applying a patch (to Emacs

Re: Problem with org-babel and geiser

Bob Heffernan writes: > I am having trouble with evaluating scheme source-blocks in org-mode. > Specifically, in a minimal example such as this: > > #+title: Test > #+PROPERTY: header-args :session *scheme* > > #+begin_src scheme > (+ 1 1) > #+end_src > > When I evaluate the src block, the

[CLOSED] TEC fixed this problem.

Today, I found the Org Agenda sorting strategy problem is fixed by commit "1b675f0ca84d637a3780cf3590308116e232fcfd". Thanks, TEC Bastien writes: > Hi, > > stardiviner writes: > >> org-agenda-sorting-strategy bug? Cannot list deadline item

Problem with org-babel and geiser

kage) (add-to-list 'package-archives '("nongnu" . "https://elpa.nongnu.org/nongnu/;)) (package-initialize) (require 'geiser) (require 'geiser-chez) (setq geiser-chez-binary "chez") (org-babel-do-load-languages 'org-babel-load-languages '((scheme . t))) but the probl

Re: Problem when tangling source blocks with custom coderefs

Hi Tom, The simplest fix right now would be to prepend your coderef > with the python comment symbols # |hello| so that at the very least it > won't break your tangled files. Actually, that is exactly what I have done as a quick fix. It has a minor inconvenience: anything else included on the

Re: Problem when tangling source blocks with custom coderefs

Hi Luis, I don't think you are doing anything wrong. IIRC the portion of the patch that allowed the customization to propagate to the tangled code was not included. Given that I am no longer the only one who is looking for/expecting this behavior, maybe it is worth revisiting the decision. The

Problem when tangling source blocks with custom coderefs

Dear all, I would like to tangle source code blocks that contain coderefs. I have found that the coderefs are correctly filtered out from the tangled files if they follow the default format, i.e. "(ref:%s)", but not if I try to customize the format using the documented "-l" switch [1] to change

add-to-list problem with ox-context

Hi all, I guess that I am not able to configure ox-context like this: #+begin_src emacs-lisp (use-package ox-context :straight (ox-context :type git :host github :repo "Jason-S-Ross/ox-context") :config (setq org-context-pdf-process '("context --mode=trimsize %f"))

Re: [bug] serious problem retrieving data from table for gnuplot

On Friday, 14 Jan 2022 at 22:01, Ihor Radchenko wrote: > Ouch. Sorry for this. This was introduced by fixing another bug. > Should be fixed on main now. Thank you for such a quick response and no worries! Yes, it seems to work now. -- : Eric S Fraga, with org release_9.5.2-306-g9623da in Emacs

Re: [bug] serious problem retrieving data from table for gnuplot

Eric S Fraga writes: > By the way, adding an empty column to front of the table fixes the > problem so at least I am not panicking (I have a presentation to give > with the data in a table etc.). There must be a problem with a regex > looking for dividing lines maybe? Sorry

Re: [bug] serious problem retrieving data from table for gnuplot

Eric S Fraga writes: > Hello all, > > as I recently updated org, I seem to have run into a bug with ob-gnuplot > (or ob more generally) where data from a table are not interpreted > correctly. Specifically, if the first column entry in a row is a > negative number, the data file created for use

Re: [bug] serious problem retrieving data from table for gnuplot

By the way, adding an empty column to front of the table fixes the problem so at least I am not panicking (I have a presentation to give with the data in a table etc.). There must be a problem with a regex looking for dividing lines maybe? -- : Eric S Fraga, with org release_9.5.2-304-g1537bb

[bug] serious problem retrieving data from table for gnuplot

Hello all, as I recently updated org, I seem to have run into a bug with ob-gnuplot (or ob more generally) where data from a table are not interpreted correctly. Specifically, if the first column entry in a row is a negative number, the data file created for use by gnuplot consists of only -

Re: Help debugging R source code block output problem with :session

On Wed, Jan 12, 2022 at 1:50 AM Jeremie Juste wrote: > > Hello John, > > Many thanks for reporting. I'm short of time right now, but I'll take a > closer look at the problem over > the weekend and keep you posted. Could you let me know which version of > org-mode you are c

Re: Help debugging R source code block output problem with :session

Hello John, Many thanks for reporting. I'm short of time right now, but I'll take a closer look at the problem over the weekend and keep you posted. Could you let me know which version of org-mode you are currently using? Best regards, Jeremie Juste On Tuesday, 11 Jan 2022 at 17:36, John

Re: Help debugging R source code block output problem with :session

Greetings, Apologies for writing off-list, but I don't have the original thread anymore to reply to. I just pulled this group in directly from the email I found... I just got bitten by this as well and burned most of my afternoon trying to figure out what the issue was. Any further thoughts on a

[SOLVED] (was: (ledger?) The fair Christmas problem: splitting expenses automatically)

>>> "UB" == Uwe Brauer writes: > Hi > I am not sure whether this is the right place to ask this, but anyhow. > Suppose two friends want to buy Christmas presents, but when they have > finished, they want to have spent the same amount of money. If they > don't a compensation must be

(ledger?) The fair Christmas problem: splitting expenses automatically

Hi I am not sure whether this is the right place to ask this, but anyhow. Suppose two friends want to buy Christmas presents, but when they have finished, they want to have spent the same amount of money. If they don't a compensation must be transferred. Here is an example ** Start #+name:

Re: execute src block during export (Re: Worg HTML export problem?)

On 12/11/2021 23:55, Thomas S. Dye wrote: Max Nikulin writes: On 12/11/2021 00:24, Thomas S. Dye wrote: The original problem is likely due to the default header arguments in ob-org.el, which are unusual. It is great that the problem is solved. I do not think however that something inside

Re: execute src block during export (Re: Worg HTML export problem?)

Aloha Max, Max Nikulin writes: On 12/11/2021 00:24, Thomas S. Dye wrote: The original problem is likely due to the default header arguments in ob-org.el, which are unusual. It is great that the problem is solved. I do not think however that something inside ob-org.el may affect

Re: execute src block during export (Re: Worg HTML export problem?)

On 12/11/2021 00:24, Thomas S. Dye wrote: The original problem is likely due to the default header arguments in ob-org.el, which are unusual. It is great that the problem is solved. I do not think however that something inside ob-org.el may affect processing of a file before this package

babel+matlab+python2.7+matlab_kernel ipython jupyter matlab: problem

Hi I am on ubuntu 16.04 with python 3.5 and 2.7 in the past I have used successfully the matlab python kernel for 3.5 Using more or less this: sudo apt-get install python3-setuptools sudo -H python3 -m pip install jupyter sudo apt-get remove python3-pexpect sudo -H python3 -m pip install

Re: execute src block during export (Re: Worg HTML export problem?)

org-contrib/babel/languages/ob-doc-org.org No org-babel-execute function for org! However I do not see explicit load/require for particular language in sibling files. I expected something like #+begin_src emacs-lisp :exports none (require 'ob-org) #+end_src Thanks for looking into this. Is t

execute src block during export (Re: Worg HTML export problem?)

No org-babel-execute function for org! However I do not see explicit load/require for particular language in sibling files. I expected something like #+begin_src emacs-lisp :exports none   (require 'ob-org) #+end_src Thanks for looking into this. Is the problem something I can fix in ob-

Re: Worg HTML export problem?

into this. Is the problem something I can fix in ob-doc-org.org? Or, does it have to do with the configuration at sr.ht? All the best, Tom -- Thomas S. Dye https://tsdye.online/tsdye

Re: Worg HTML export problem?

On 08/11/2021 05:46, Thomas S. Dye wrote: I pushed a new file, ob-doc-org.org, to Worg earlier today, but the link in https://orgmode.org/worg/org-contrib/babel/languages/index.html gives a 404 error.  I usually see this when the Org file has a bad link that causes export to fail, but AFAICT

Worg HTML export problem?

Aloha all, I pushed a new file, ob-doc-org.org, to Worg earlier today, but the link in https://orgmode.org/worg/org-contrib/babel/languages/index.html gives a 404 error. I usually see this when the Org file has a bad link that causes export to fail, but AFAICT ob-doc-org.org doesn't have

Re: problem with columnview and the match option

>>> "IR" == Ihor Radchenko writes: > Uwe Brauer writes: >> ** All groups >> #+BEGIN: columnview :hlines 2 :match "H1" :maxlevel 2 >> :skip-empty-rows t :indent nil :format "%5TODO(Status) %5Id(Group) >> %5Ex(Exercise) %5Sheet(Sheet) %7ST1(Status){X/}" >> | Status | Group | Exercise | Sheet |

Re: problem with columnview and the match option

Uwe Brauer writes: > ** All groups > #+BEGIN: columnview :hlines 2 :match "H1" :maxlevel 2 :skip-empty-rows t > :indent nil :format "%5TODO(Status) %5Id(Group) %5Ex(Exercise) > %5Sheet(Sheet) %7ST1(Status){X/}" > | Status | Group | Exercise | Sheet | Status | >

problem with columnview and the match option

Hi Please look at this example #+begin_src lisp * Sheets :noexport: :PROPERTIES: :COLUMNS: %10SSheet(Sheet Nr) %10Ex(Exercise Nr) %17Date(Date) %7STATUS(Status){X/} :ID2: Sheet1 :END: ** DONE G1

likely re-order date problem solution

I think I figured out how to make re-order dates work in orgmode. The start date is the date when items start getting used. So subtract the number of weeks before the next order is needed from the start date and write that time stamp in with a + repeater value to cover the days until the next

Re: table: problem with nan and if

> Uwe Brauer writes: > Could you write the formulas in lisp instead? You might be able to control > things more easily: Aha, that I will try. Thanks for pointing it out. So it seems that my question is not trivial. smime.p7s Description: S/MIME cryptographic signature

[SOLVED] (was: some progress matlab-kernel, a python path problem?)

>>> "JK" == John Kitchin writes: > I would see if you can open a jupyter notebook and start a notebook with > the mat lab kernel. If not, it either isn’t installed, or maybe is > installed in a different jupyter. > If you get errors here, the issue is outside of org mode. For example, the >

Re: table: problem with nan and if

Uwe Brauer writes: >> Uwe Brauer writes: > > >> I'm not very familiar with calc, but am wondering if the issue is the >> 'nan'. In many languages, a nan is a 'polluting' variable i.e. once you >> have a nan as a form anywhere in your calculation, the result will >> always be a nan. Many

Re: table: problem with nan and if

>>> "t" == tbanelwebmin writes: > About the E format setting, you may look at documentation here: > [[info:org#Formula syntax for Calc]] Thanks I tried, but I think the core of the problem is that $7 needs two ifs with two commands #+begin_src elisp Case I $6

Re: table: problem with nan and if

>>> "ESF" == Eric S Fraga writes: > Uwe, > what if you change the E in each equation with N? You'll get 0 entries > when the calculations involve all empty cells which might not be what > you want, of course. In that case I obtain a 0, which I don't want smime.p7s Description: S/MIME

Re: table: problem with nan and if

About the E format setting, you may look at documentation here: [[info:org#Formula syntax for Calc]] Le 22/06/2021 à 09:44, Eric S Fraga a écrit : > Uwe, > > what if you change the E in each equation with N? You'll get 0 entries > when the calculations involve all empty cells which might not be

Re: table: problem with nan and if

Uwe, what if you change the E in each equation with N? You'll get 0 entries when the calculations involve all empty cells which might not be what you want, of course. -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-566-gf0198e : Latest paper written in org:

Re: table: problem with nan and if

> Uwe Brauer writes: > I'm not very familiar with calc, but am wondering if the issue is the > 'nan'. In many languages, a nan is a 'polluting' variable i.e. once you > have a nan as a form anywhere in your calculation, the result will > always be a nan. Many languages actually have a special

Re: table: problem with nan and if

" == "nan", string(" "),0.3*$5+0.6*$6); E f-1 > #+end_src > > > The calculations for User2 and 3 are fine, but for User1, the final > result is a "nan". > > I see the problem is caused by ; E f-1 I don't understand why because > > As in >

Re: table: problem with nan and if

5, and $7 are calculated. If column $2,$3, and $4 are non empty $5 is just the sum of these. The problem is $7: 1. it should be the sum of $5 and $6, *even* if $5 is empty, 2. but it should be empty if $6 is empty. #+begin_src elisp #+NAME: test | Name | E1 | E

Re: table: problem with nan and if

Uwe, it might be easier if you explained what it is you want to do (at a higher level) instead of trying to get us to help to fix what you have done? -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-566-gf0198e : Latest paper written in org: https://arxiv.org/abs/2106.05096

table: problem with nan and if

for User2 and 3 are fine, but for User1, the final result is a "nan". I see the problem is caused by ; E f-1 I don't understand why because As in #+begin_src elisp | user1 | User2 | | |---+---+-| | | 3 | nan | | 0 | 1 | 0.8 | #+TBLFM: $3=0.2*$1+0.8*$2

Re: Problem inserting meeting in agenda using "pm" time indicators

On Friday, 18 Jun 2021 at 14:14, Nicolas Goaziou wrote: > Duh. Fixed. Thank you. Confirmed! Thank you. :-) -- : Eric S Fraga via Emacs 28.0.50, Org release_9.4.6-557-gceb78e : Latest paper written in org: https://arxiv.org/abs/2106.05096

<    1   2   3   4   5   6   7   8   9   10   >