Re: outline-minor-mode and org-mode capabilities for programming languages

> I have same elisp code and using outline-minor-mode. The good thing about it > is that > the language highlighting is preserved. But navigating and moving the code > around is > much more difficult than actually being in org-mode (I can use tab ate move > code with > "M-", M-). The

Re: [PATCH] ox-bb.el: Add BBCode exporter

Hellp Bastien, On Mon, Apr 26, 2021 at 09:49:13AM +0200, Bastien wrote: > Christian Garbs via "General discussions about Org-mode." > writes: > > > after getting an encouraging reply to my initial proposal[1], I went > > forward and finished the patch to inc

Custom link type that attaches file in :follow

Hi! I am having some trouble adding a link via =org-link-set-parameters=. I want to have a custom =xournalpp=-link type that behaves as follows: - follow :: Open attached file - exists :: open the file - don't exist :: create attachment directory and copy template file into it - export ::

Bug: Incompatible return type in org-babel C when using a table of doubles with a header as a variable [9.4.4 (release_9.4.4-272-ga9f38b @ /home/richard/.emacs.d/straight/build/org/)]

When a table of floating pointer numbers that contains a header row is set as a variable to a C source block, the generated header file contains an invalid return type, causing the program to not compile. For example, if I have a table that looks like #+NAME: tbl-doubles-org-bug-report

Re: Bug: Org bold emphasis gobbles leading stars on next headline [9.3.7 (release_9.3.7-710-g3f04ad @ /home/n/.emacs.d/straight/build/org/)]

> No Wayman writes: > > With the following Org mode file and point denoted by "|": > > > > * Parent > > | > > ** Sibling > > > > Insert the text "*", resulting in: > > > > * Parent > > "*"| > > ** Sibling > > > > textually, but the final star of the Sibling heading is hidden as > > well: > > > >

org agenda bug — diary-sexp-entry-symbol is not respected

The string "%%" is hard coded here as a date prefix: https://code.orgmode.org/bzg/org-mode/src/master/lisp/org-agenda.el#L5648 Shouldn’t this be diary-sexp-entry-symbol to allow local overrides, etc.? -- Dr Joseph A. Corneli (https://github.com/holtzermann17) HYPERREAL ENTERPRISES LTD is a

org agenda bug — respect literal examples

Org Agenda seems not to respect lines beginning with ":" or other literal examples. E.g., adding a line like this will populate the Org Agenda: : (<%%(diary-float t 3 -1)> in org-mode) Similarly for: #+begin_src org (<%%(diary-float t 3 -1)> in org-mode) #+end_src #+begin_src emacs-lisp ;;

[PATCH] ox-bb.el: Add BBCode exporter

Hi, after getting an encouraging reply to my initial proposal[1], I went forward and finished the patch to include the BBCode exporter in Org. The patch applies to current master and includes a suite of tests. Please review and/or apply this patch. Best regards, Christian [1]

Re: [bug] Exporting results in "Wrong type argument" when "+CALL" is used

> On Jan 30, 2021, at 3:10 PM, Rodrigo Morales > wrote: > > > As the subject states, executing some exporting commands (see list in > step 2 below) results in an error when there is at least one "#+CALL" > statement. > > The backtrace is shown below. > > #+begin_example > Debugger

Re: Regression in org-element-fixed-width-parser? Extra newline added after exported block

On Tue, Jan 19, 2021 at 08:45:22PM +0100, mitch--- via General discussions about Org-mode. wrote: > I have created a minimal test using the ox-ascii backend that shows > the same behaviour in Org core. Which is attached here because it forget it in the original mail. Sorry Christian

Regression in org-element-fixed-width-parser? Extra newline added after exported block

Hi all, I wrote two Org exporters[1,2] that each have a testsuite of their own. I regularly run tests against Emacs 25 and 26 with their respective Org versions. When I started to test against Emacs 27.1 with Org mode 9.3 I got test failures in both exporters: The export of a fixed with block

How to not include newlines in strip-export?

I'm using the following snippet for saving the plot in python snippets #+NAME: save-file #+BEGIN_SRC python :results silent :var filename="filename" plt="plt" :exports none return f"\nfname = 'assets/' + filename + '.png'\nplt.savefig(fname)\nfname" #+END_SRC Using it like so #+BEGIN_SRC

[PATCH] testing/lisp/test-org-archive.el: Fix test

Hello, I've run across a test error on the current HEAD. When I run "make test" on my system, then test-org-archive/datetree fails. The test fails because the expected output should contain "Sunday", but with a German locale the generated text is "Sonntag" instead (which is the German

Bug: test-org-archive/datetree fails with German locale

Hello, I've run across a test error on the current HEAD. When I run "make test" on my system, then test-org-archive/datetree fails. The test fails because the expected output should contain "Sunday", but with a German locale the generated text is "Sonntag" instead (which is the German

proposal: ox-bb, Org exporter for BBCode

Hi there, I wrote a simple Org exporter[1] for the BBCode format[2] which is used in many web forums. Is there any interest in including it in Org? Known todos on my side are: 1. Rewrite my shell tests in elisp to include then in the Org tests. 2. Figure out a test error on Emacs 27. I

[PATCH] ox.el: Add missing polish translations in export dictionary

Hi All, This patch is just a quick addition to export dictionary for polish language. Things which were translated: - Continued from previous page -> Ciąg dalszy poprzedniej strony - Continued on next page-> Kontynuacja na następnej stronie Let me know if it's ok. Karol Wójcik>From

Re: patch: ob-clojure improvements

Nice work, I did some testing here... * Comment: Should babashka be added as an option for custom? (defcustom org-babel-clojure-backend nil "Backend used to evaluate Clojure code blocks." :group 'org-babel :type '(choice (const :tag "inf-clojure" inf-clojure) (const

Re: Bug: DOI links are broken in HTML exports

Thanks Bastien. > Do you use a link abbreviation for doi: links ? > >> When I export this document to HTML the DOI link gets converted into a >> broken hyperlink. It should be converted into >> https://doi.org/10.1186/s12864-016-2377-z as explained >> in https://www.doi.org/.

Bug: DOI links are broken in HTML exports

Hi, I've found a small bug in org-html-export-to-html. Minimal document to reproduce: --- Foo [fn:1] * Footnotes [fn:1] doi:10.1186/s12864-016-2377-z --- When I export this document to HTML the DOI link gets converted into a broken hyperlink. It should be converted into

Re: basic org questions

Alexander Adolf wrote: > I use visual-line-mode (which also enables > word-wrap by default) for Org files. For instance: > > (add-hook 'org-mode-hook (lambda () >(turn-off-auto-fill) >(visual-line-mode) >

Re: basic org questions

Stefan Nobis wrote: >>> #+attr_latex: :center nil :booktabs t >>> | My | Columns | >>> |+-| >>> | 1 | 2 | >>> | 3 | 4 | > >> "PDF file produced with errors." > > Sorry that I try to make more general examples that > are not exactly tailored to your use case. > As I said

Re: basic org questions

Stefan Nobis wrote: >> There are many pieces of software that will allow >> the user to the violate best typesetting practices >> easily. LaTeX is not one of them. > > Not quite right. I have seen people create really > ugly source code *and* ugly output with LaTeX with > ease. You can create

Re: basic org questions

Stefan Nobis wrote: >> OK, but the values still ned to be >> specified, right? > > No, just use the package - it sets the relevant > lengths to change the style of marking paragraphs > and tries hard to also reset every other length > that depends on the original values of > these variables. You

Re: basic org questions

Nick Dokos wrote: > (setq org-latex-tables-centered nil) Yes! :) Thanks :) That took a couple of messages... :O -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal

Re: basic org questions

Thomas S Dye wrote: > There are many pieces of software that will allow > the user to the violate best typesetting practices > easily. LaTeX is not one of them. In my experience, you can typeset whatever you want with LaTeX, and in any way that you want. non-fiction book:

Re: basic org questions

Stefan Nobis wrote: > #+attr_latex: :center nil :booktabs t > | My | Columns | > |+-| > | 1 | 2 | > | 3 | 4 | "PDF file produced with errors." -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal

Re: basic org questions

tomas wrote: > Or just ask around here, but best with concrete, > little goals each time. ? -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal

Re: basic org questions

TEC wrote: > You see, strangely enough - if you want to tweak > the result of Org exporting to LaTeX, you have to > write LaTeX :P I got it to work. Thanks for your help. I'm not abandoning org-mode just yet... -- underground experts united http://user.it.uu.se/~embe8573

Re: basic org questions

Samuel Wales wrote: >> Marking paragraphs by blank lines and without >> indentation is deemed less readable (see for >> example section 3.10 "Marking Paragraphs" in >> https://komascript.de/~mkohm/scrguien.pdf). [...] > > for my part, i appreciate your using the "wrong" > style for your email

Re: basic org questions

Stefan Nobis wrote: >> #+latex_header: \setlength{\parindent}{0pt} >> #+latex_header: \setlength{\parskip}{\baselineskip} > > Better use > > #+latex_header: \usepackage{parskip} > > as this package has less bad side-effects on other > parts of the document than setting these far-reaching >

Re: basic org questions

Stefan Nobis wrote: > But otherwise I second your recommendation to not > use this style of marking paragraphs if not > absolutely required. Well, I'm not exactly required to do anything, but I know what I think something should look like... -- underground experts united

Re: basic org questions

Tim Cross wrote: >> #+latex_header: \parskip 1.5ex >> #+latex_header: \parindent 0pt > > Note that I agree with the other post recommending > using the parskip package as a better solution. > I had forgotten about that package when I posted > the above, which is really just a dirty hack.

Re: basic org questions

Tim Cross wrote: > #+latex_header: \parskip 1.5ex Got it! Thanks! Now it works, with: #+latex_header: \parskip 1.5ex #+latex_header: \parindent 0pt -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal

Re: using header data in document

Eric S Fraga wrote: > what does your #+date: line look like? Is it > a single time stamp? If it is not, all of the above > would return the same thing. I don't have that line. -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal

Re: using header data in document

Eric S Fraga wrote: >> {{{date()}}} works as does {{{date(%D)}}} in >> a sense, only the format string doesn't seem to >> influence the output, which is "September 16, >> 2020". > > The documentation that you have in your post says > that this works only if the actual date given in > the #+DATE

Re: using header data in document

Eric S Fraga wrote: > On Wednesday, 16 Sep 2020 at 00:08, Emanuel Berg via > "General discussions about Org-mode." wrote: > >> Hm, date? Maybe that can be used to do a line like >> the LaTeX's >> >> Last modified: \today >> >> or how would

Re: basic org questions

Tim Cross wrote: > #+latex_class: korma-article user-error: Unknown LaTeX class ‘korma-article’ > #+latex_header: \setlength{\parindent}{0pt} Yes, that's removed the indentation but didn't insert a blank line... -- underground experts united http://user.it.uu.se/~embe8573

Re: basic org questions

Matt Huszagh wrote: >> Yeah, but in LaTeX being left aligned is not some >> property of the table, everything is left-aligned, >> and if you want it otherwise, you put between >> \begin{center} and \end{center} ... > > That page also describes how to set float > parameters, which the table can be

Re: using header data in document

Corwin Brust wrote: > | Org comes with following pre-defined macros: > | > | ‘{{{keyword(NAME)}}}’ > | ‘{{{title}}}’ > | ‘{{{author}}}’ > | ‘{{{email}}}’ Thanks, great! > So you can use use, e.g. {{{author}}} in various > places to get at data from the header: > > | Org recognizes macro

using header data in document

How can I use header data in the document? E.g., #+AUTHOR: Emanuel Berg [...] \author I wrote this! # only that doesn't work -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal

Re: basic org questions

Matt Huszagh wrote: > Were you referring to the tables being centered > after export (I see from another part of this chain > that that's what you were referring to in the 3rd > question) when you wanted them left-aligned? > If that is the case, it would really help if you > specify that in your

Re: "text mode" org mode

Stefan Nobis wrote: >>> (setq org-link-descriptive nil) >> >> I don't have org-link-descriptive, it seems... > > No problem, the old name is =org-descriptive-links= > (this name has been deprecated in Org 9.3, but it > is still working in 9.4). Thanks, I wonder tho if all this (setq

Re: basic org questions

Matt Huszagh wrote: > If you mean the table itself, that would be > very strange. Heh...? What's strange with that? Anyway that's what I mean. -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal

Re: basic org questions

tomas wrote: > The variable `org-emphasis-regexp-components' is > documented, so one might hope that the method is > magic, but somewhat official. Indeed, that works: (setq org-emphasis-regexp-components (append (butlast org-emphasis-regexp-components) '(7)) ) :) -- underground

Re: basic org questions

Re: basic org questions Russell Adams wrote: >> 1) How do I make a region italic? [...] > > https://emacs.stackexchange.com/questions/18101/org-mode-multi-line-emphasis-and-bold OK, thanks, not the same good looking syntax tho but good enough for government work, I suppose. >> 2) How do I have

basic org questions

1) How do I make a region italic? This does not fontify and does not show up as italic type: /En gång i tiden var även Spanien täckt av skog. En gammal berättelse menar att man i norra Spanien kunde hoppa upp på en apas rygg och ta sig ner till södra Spanien utan att klättra av en enda gång.

Re: "text mode" org mode

Stefan Nobis wrote: > (setq org-link-descriptive nil) I don't have org-link-descriptive, it seems... Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ /usr/share/emacs/26.1/lisp/org/) GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu) of 2019-09-23, modified by Debian -- underground experts

Re: "text mode" org mode

Gustavo Barros wrote: > That's probably not something most Org users would > do, but I think you'd get close to what you want > with: > > (add-hook 'org-mode-hook 'visible-mode) Yeah, that seems to have done it? Great! Thanks a lot! ;;; -*- lexical-binding: t -*- ;;; ;;; this file: ;;;

Re: "text mode" org mode

Russell Adams wrote: > I believe you can set your #+STARTUP on your file > to "showall". Can I prevent hyperlinks from folding back and forth? I mean, with [[][]] ? Hm, maybe this will just go on and on if there is no option to do it for real. The font-lock idea was perhaps not so bad...? --

Re: "text mode" org mode

> Can I tell Org mode to don't change editing back > and forth, also don't collapse items in and out, > i.e. virtually text mode, only I still want the > font lock and to be able to use the mode to set > keys, the functions to compile into a PDF, and > so forth. Here is part of an IRC

Re: "text mode" org mode

Russell Adams wrote: > I believe you can set your #+STARTUP on your file to "showall". That's a good, uhm, start! Thanks. > This will make the whole file open. I don't know if > you could disable tab folding a drawer > later though. Well, I can rebind that key... -- underground experts

Re: All the best

edgar wrote: > I just want to send a small note to wish you the best > during these times of need. Let us remember that it is > community which allows us to keep going as a species. > Please, take care of yourselves and those who surround > you, and let us do our best to overcome the >

"text mode" org mode

Can I tell Org mode to don't change editing back and forth, also don't collapse items in and out, i.e. virtually text mode, only I still want the font lock and to be able to use the mode to set keys, the functions to compile into a PDF, and so forth. TIA -- underground experts united

Re Org 9.4 is out. Can you help? // breaking apart Org Mode

Hello, At the request of Bastien I'm sending on these ideas regarding the future of Org Mode development. I'm also copying emacs-devel since they might be interested too. Org Mode and Emacs would benefit greatly from the codebase being broken apart, not unlike how an antitrust suit breaks

[BUG?] org-edit-src-save active in Org-Babel Previewo

In an babel preview buffer opened with 'org-babel-expand-src-block, ('org-edit-src-save) writes the expanded view back to the org file, with all the variable expansions, etc. I may be wrong, but i don't remember this behavior in older versions of Org, and this has bitten me a couple of times,

Bug: Link descriptions include checkbox counter [9.3.7 (9.3.7-16-g521d7f-elpaplus @ /home/tarjei/.emacs.d/elpa/org-plus-contrib-20200803/)]

Hi! Is it intended behavior for =org-store-link= to include checkboxcounters in the description? I would expect the example below to be =[[id:..][Link to this]]=, similarly to how TODO keywords are treated. #+begin_src org ,*** [1/2] Link to this :PROPERTIES: :ID:

Bug: Attachment directory omitted from html export if line 1 is not section heading [9.3.7 (9.3.7-14-gb2b587-elpaplus @ /home/tarjei/.emacs.d/elpa/org-plus-contrib-20200720/)]

Hi! The following org file, where the attachment is a copied text file, is exported to a fully functional html page: -- without_title.org --- * Section :ATTACH: :PROPERTIES: :ID: 17b1efb9-e20c-4637-98c1-12e796e18d62 :END: Attachment link to attachment

Re: Anyone doing any fancy customizations of source blocks?

Hi Bill, I'm glad you found the example useful. I've been thinking myself of also un-hiding the header arguments, which I do find useful to have visible. Best, --Diego On Fri, Jun 19, 2020 at 4:04 AM William Denton wrote: “On 3 June 2020, Diego Zamboni wrote: > I use the config John mentioned

FWD: Re: FWD: Org-Babel Support for Powershell

Hi, I thought about four possible solutions to include Powershell 7 in Emacs. I understand that Powershell 5.1 is not Open Source. But is is not the case with Powershell 7. I share my idea with nche...@linuxha.com below. I am still not very familiar with the vast emacs universe. But I am very

FWD: Org-Babel Support for Powershell

Hi, I ask the maintainer of org-babel Bastien Guerry , if it is possible to include Powershell support for org-babel. Monsieur Guerry told me to ask you via email. Powershell 5.1 is now an important tool for Infrastructure as Code in the Windows Server world. Windows

bug#41364: 27.0.91; org-self-insert-command does not work

Hi Tim, you need to add (require 'org-tempo) to your configuration to get writes: > Tim Hawes writes: > >> Start emacs with emacs -Q >> Start or open an org-mode document >> type > describe-key looks correct. > > Does the following snippet from ORG-NEWS's "incompatible changes" > section[1]

Re: Bug: Repeating tasks no longer appearing on future dates in the agenda [9.3.6 (9.3.6-17-g389288-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200224/)]

Hi Gustavo, Gustavo Barros writes: > Hopefully a solution for the one-time delay issue which does not > trigger this new problem can be found. But I concur (if I may) it was > a wise decision to revert the commit in the meantime. Agreed, thanks Kyle. I'll revisit the one-time delay issue

Re: Public API change: How to handle function signature change gracefully

Thanks John and Nicolas. I sort of arrived at the same point with my over-engineered approach and change of public API. modified   lisp/org.el @@ -5081,10 +5081,18 @@ This includes angle, plain, and bracket links." (link (org-element-property :raw-link link-object)) (type (org-element-property

Public API change: How to handle function signature change gracefully

Hello everyone, I would like to change the public API of the :face part of `org-link-set-parameters':     (org-link-set-parameters "file" :face 'org-link) My ultimate goal is to have org-links be able to be have their face changed based on the contents, not just the path of the link. I

<    1   2   3