Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

Ihor Radchenko writes: > If you want, I can test the file without :LOGBOOK: lines tomorrow. Don't worry, it doesn't matter now. > No, there are only 9 'outline overlays in the folded buffer if we do not > create overlays for drawers. This is because outline-hide-sublevels > called by org-overvi

Re: "\_" sequences in indented lines of column view dynamic blocks

ligned otherwise. 2. They preserve indentation upon export. > I just find them ugly and irritating. Sorry about that. Note it is our best idea to solve both problems so far. It you have something better, please tell us! Regards, -- Nicolas Goaziou

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

Ihor Radchenko writes: > My response to you was blocked by your mail server: > >> 550 5.7.1 Reject for policy reason RULE3_2. See >> http://postmaster.gandi.net Aka "spam detected". Bah. > The message landed on the mail list though: > https://www.mail-archive.com/emacs-orgmode@gnu.org/msg127972

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

Ihor Radchenko writes: > I still do not feel much difference, so I used elp to quantify if there > is any difference I cannot notice by myself. I tested the time to move > from to bottom of the example file with next-logical-line. > > org master (7801e9236): > 6(#calls) 2.852953989(tota

Re: patch for org-capture.el to allow for no file extension on open-source, protocol

fix to not be required. Thank you. Could you add a test in "test-org-protocol.el" ? Regards, -- Nicolas Goaziou

Re: [Patch] Do not ignore headers argument in ob-latex

el-execute:latex'. But it may not make much sense, indeed. Regards, -- Nicolas Goaziou

Re: Bug: Images with link break LaTeX export with centered images [9.3.6 (9.3.6-elpa @ /home/arne/.guix-profile/share/emacs/site-lisp/)]

; > To reproduce: use linked image syntax like this: > > > [[file:covid-19-germany-infections-by-date-prognosen-2020-03-23.png][file:covid-19-germany-infections-by-date-prognosen-2020-03-23.png]] Fixed. Thank you. Regards, -- Nicolas Goaziou

Re: [RFC] Let Org Mode's completion support all Babel header arguments

PI to manage those keywords. WDYT? pcomplete certainly needs some love. There is already `org-babel-common-header-args-w-values' and `org-babel-header-args:LANG'. You may want to look into `org-lint-wrong-header-value' to check how they are used. Regards, -- Nicolas Goaziou

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

n in the same. Of course, that case happens less often with text properties. For example, it happens in "contents" view in both cases. However, in "show all" view, it is only a problem with overlays. Regards, -- Nicolas Goaziou

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

Ihor Radchenko writes: > Note that the following commits seems to break my patch: Unfortunately, I don't see your patch.

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

n a headline with several levels of subheadings moves > the cursor to the end of subtree, which did not happen in the past. Indeed. I fixed that, too. Thank you! Regards, -- Nicolas Goaziou

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

Nicolas Goaziou writes: > I wonder how it compares to drawers using the same invisible spec as > headlines, as it was the case before. Could you give it a try? > > I think hiding all property drawers right after opening a subtree is > fast enough. As a follow-up, I switched p

Re: [PATCH] Fix moving cursor in org-set-tags-command

t Lundin's solution (with skip-chars-backward), along with your tests! Regards, -- Nicolas Goaziou

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

restore-invisibility-specs) Ouch. I hope we can avoid that. I wonder how it compares to drawers using the same invisible spec as headlines, as it was the case before. Could you give it a try? I think hiding all property drawers right after opening a subtree is fast enough. Another option, as I already suggested, would be to use text-properties on property drawers only. Ignoring isearch inside those sounds tolerable, at least. Regards, -- Nicolas Goaziou

Re: [PATCH] faster org-table-align

t; > Just replace them by a call to `org-table-to-lisp': > > (fields (cl-loop for row in (org-table-to-lisp) > collect (and (listp row) row))) Good catch! I applied a similar change in master. Let me know how it goes. Thank you! Regards, -- Nicolas Goaziou

Re: [PATCH] Fix moving cursor in org-set-tags-command

ab*|c where "|" is point. Besides, I don't understand how this is related to empty headlines since, AFAICT, this part of code is supposed to fix the issue on empty headlines. Regards, -- Nicolas Goaziou

Re: [Bug]: org-capture-place-plain-text error when template :unnarrowed

And a minimal passing case: > > #+begin_src emacs-lisp > (let ((org-capture-templates >'(("t" "test" plain (file "/tmp/bug.org") > "PASS%?" :unnarrowed t > (org-capture nil "t")) > #+end_src Fixed. Thank you. Regards, -- Nicolas Goaziou

Re: [Patch] Do not ignore headers argument in ob-latex

t-file org-format-latex-options in-buffer))) This looks hackish but I don't know how to do it otherwise. However could you use `mapconcat' instead of `string-join'? Also, you need to declare `org-format-latex-header' in order to silence byte-compiler. Regards, -- Nicolas Goaziou

Re: [PATCH] Allow org-capture-mode-hook to access org-capture-current-plist [9.3.6 (release_9.3.6-443-g0e8aff @ /home/n/.emacs.d/straight/build/org/)]

in the commit message, add TINYCHANGE cookie if you haven't signed FSF papers yet, and add an entry in ORG-NEWS about it? Regards, -- Nicolas Goaziou

Re: [PATCH] Make RET and C-j obey `electric-indent-mode' in org-mode

Kévin Le Gouguec writes: >> (I hope I got that right.) LGTM. I applied the patch on your behalf. Now Org has future-proof support for Electric indent mode. Thank you.

Re: [PATCH] Make RET and C-j obey `electric-indent-mode' in org-mode

Kévin Le Gouguec writes: > I see you've removed ARG from the call to `newline-and-indent'; I don't > have a strong opinion about this (though I don't see a reason not to > keep it), but I guess the docstring of `org--newline' should be changed > to match? AFAICT, `newline-and-indent' doesn't acc

Re: [PATCH] Make RET and C-j obey `electric-indent-mode' in org-mode

0 This is a nice macro. However, when I have to reproduce a failing test, I don't even want to think about the recipe and rather concentrate on the results. Hence, I expect `should' macro's body to be self-sufficient. Therefore, I skipped this part of the patch. Regards, -- Nicolas Goaziou

Re: Additonal slashes in URI sent to org-protocol

name) "?"))) > +(new-style (string-match (match-string 1 fname) "/*?"))) I don't understand this line. Aren't you calling string-match backwards? I think you mean: (new-style (string-match "?" (match-string 1 fname))) Could you also insert a comment explaining why this workaround is required? Regards, -- Nicolas Goaziou

Re: Bug: menu item: Add Source Example [9.2.6 (9.2.6-dist @ /path/to/org/install/emacs/site-lisp/org/)]

asize t] > ["Add Source Example" org-insert-structure-template t] ;; << please > add > ["Edit Source Example" org-edit-special t] > > This way it's easy to both add or edit them for people who don't have > the key bindings memorized. Done. Thank you. Regards, -- Nicolas Goaziou

Re: Scheduling in a narrowed subtree: Bug?

; > As a result, the SCHEDULED keyword is _not_ included in the narrow view, > and inserting things after the Test heading moves the SCHEDULED keyword > away from its second-line position. Fixed. Thank you. Regards, -- Nicolas Goaziou

Re: Bug: org-ellipsis does not work as a local variable [9.3.1 (release_9.3.1-95-gf93020 @ /home/mark/git-repos/org-mode/lisp/)]

meant to be a set as a local variable in its docstring. Patches are welcome to enable it, tho. Thank you for the report. Regards, -- Nicolas Goaziou

Re: Fwd: Support compilation of Haskell in org mode babel blocks.

Hello, Roland Coeurjoly writes: > Please see attached patch. Great! It seems that this is a patch that needs to be applied on top of the previous one. Could you merge them into a single patch and send it again? Please let me know when the FSF registers you. Regards, -- Nicolas Goaziou

Re: bug org-open-at-point zotero link

Hello, Charles Millar writes: > Have I missed documentation that states that "org-open-at-point os not > available for a Zotero (Zotxt) link? I don't know what is Zotxt. You way want to report the issue upstream. Regards, -- Nicolas Goaziou

Re: Fwd: Support compilation of Haskell in org mode babel blocks.

Roland Coeurjoly writes: > I am confused about the last point: > Use a let-binding instead of setq. > > If I use: > > (let* compile (string= (cdr (assq :compile params)) "yes")) I meant: (let ((compile (string= "yes" (cdr (assq :compile params) ...)

Re: Fwd: Support compilation of Haskell in org mode babel blocks.

Roland Coeurjoly writes: > I have read the page about signing FSF papers, but I am unclear about how > to proceed. > Could you give some pointers? Certainly. See https://orgmode.org/worg/org-contribute.html#copyright-issues You basically need to fill a form and send it to ass...@gnu.org. Th

Re: Document level property drawer position

global property drawer must be located at the top of the document. A comment is tolerated before it, tho. Regards, -- Nicolas Goaziou

Re: [Patch] Document org-capture-templates entry type default strings

ays. Could you send it again with a commit message more in line with our habits (variable modified, etc), and two spaces at the end of sentences? Thank you. Regards, -- Nicolas Goaziou

Re: Fwd: Support compilation of Haskell in org mode babel blocks.

Roland Coeurjoly writes: > lisp/org/ob-haskell.el | 76 +++--- > 1 file changed, 71 insertions(+), 5 deletions(-) I forgot to say a change of this size requires you to sign FSF papers. Please consider doing so if that's not already the case. Thank you.

Re: Fwd: Support compilation of Haskell in org mode babel blocks.

> + ))) Please move the closing parens on the line above. > + > +(defun org-babel-interpret-Haskell (body params) Why capitalization in function names? >(require 'inf-haskell) >(add-hook 'inferior-haskell-hook > (lambda () > @@ -96,6 +154,14 @@ org-babel-execute:haskell > (org-babel-pick-name (cdr (assq :rowname-names params)) > (cdr (assq :rowname-names params)) > > + > +(defun org-babel-execute:haskell (body params) > + "Execute a block of Haskell code." > + (setq compile (string= (cdr (assq :compile params)) "yes")) Use a let-binding instead of setq. Could you send an updated patch? Regards, -- Nicolas Goaziou

Re: Babel Haskell. Print all results when header has :results output

en't, you need to add TINYCHANGE cookie in your commit messages (and consider signing them, of course!). Regards, -- Nicolas Goaziou

Re: Reconciling org-mode idiosyncrasies with Emacs core

> > (defun org-return-and-maybe-indent () > (interactive) > (org-return (not electric-indent-mode))) I think so. Then we can mark `org-return-indent' as obsolete and suggest to call `org-return' instead. Regards, -- Nicolas Goaziou

Re: error message at line break

pected, since you force Org to use a function which is not adequate. I'm not sure we should paper over this kind of misuse of `auto-fill-function'. WDYT? Regards, -- Nicolas Goaziou

Re: wip-cite status question and feedback

It seems you didn't copy the list. I add it again. > No, I think that should be fine. (Perhaps also a fourth one for > author-only. And what about nocite?) Sorry. I wasn't clear. There is still full support for styles behind the suggested syntax, e.g., [cite/author: ...], [cite/nocite: ...] (thi

Re: wip-cite status question and feedback

hing like. ((citation ... (citation-reference :key "harry83" :suffix " at \bold{0:23:18}"))) In particular, does Citeproc handle raw LaTeX, or more generally, any code in (pre|suf)fix, as long as the locator is accessible? I assume so, but I'd rather ask. Regards, -- Nicolas Goaziou

Re: Possible bug in subtree matching with empty title + tags

we cannot support both, choosing one breaks support for the other. You could use, e.g., a NO-BREAK SPACE character in your headline and lift the ambiguity. This is not a change, but rather and undefined corner-case. There was a discussion about it a couple of years ago, IIRC. I don't remember what the outcome was. Regards, -- Nicolas Goaziou

Re: wip-cite status question and feedback

Hello, Richard Lawrence writes: > If so, then I think Nicolas' proposal to have "cite" mean default and > make non-default citations available as "cite/xxx" makes sense > (especially with the other syntax supporting suppress-author, etc.). > > If not, the

Re: wip-cite status question and feedback

ocessor to each export back-end. The same processor can be associated to multiple export back-ends. Moreover, you can change this association globally, or per document. Is that sufficient? Regards, -- Nicolas Goaziou

Re: [ANN] faster org-table-to-lisp

t; > (org-table-to-lisp) Indeed. Done. Thank you. Regards, -- Nicolas Goaziou

Re: [ANN] faster org-table-to-lisp

tbanelwebmin writes: > I realized that not calling `org-table-end' may cause a corner case: > > | 2 | b | > | c | d | > > #+TBLFM: @1$1=2||3 Indeed. I also realized this, and fixed it a couple of hours ago. You will notice I shamelessly used your "\\="© trick! :) > I do agree. We can expect cal

Re: [ANN] faster org-table-to-lisp

Hello, tbanelwebmin writes: > Nicolas, how did you do that? Your version is 25% faster than mine, > and the code is 33% shorter! Very elegant. Thank you. There's nothing fancy, really. The main difference is that it does not call `org-table-end'. Minor tweaks are: - use

Re: [ANN] faster org-table-to-lisp

tbanelwebmin writes: > I found a way to ensure full backward compatibility. I keep the same > signature. When a table is given as a string parameter, it is inserted > into a temporary buffer, which is then parsed. Overall, the resulting > speed is quite satisfactory. A, you didn't like my EL

Re: Bug: org-preview-latex-process-alist's :latex-header should not fall back to org-format-latex-header [9.3.4 (9.3.4-5-ga0f3bb-elpaplus @ /home/lockywolf/.emacs.d/elpa/org-plus-contrib-20200210/)]

a different compiler. IIRC, LATEX_HEADER_EXTRA is meant for non-preview compilation. LATEX_HEADER is for both preview and export. Regards, -- Nicolas Goaziou

[RFC] Change default value for `org-startup-folded'?

rg folding the hard way. WDYT? Regards, -- Nicolas Goaziou

Re: [ANN] faster org-table-to-lisp

acted from the buffer. You are right. I guess the initial implementation didn't have these monster tables in mind. > This function is a drop-in replacement for the standard one. It can > benefit to Babel and Gnuplot. > > Would it make sense to upgrade Org Mode code base? Certainly. Could you add an entry in ORG-NEWS, in "Miscellaneous"? Regards, -- Nicolas Goaziou

Re: Reconciling org-mode idiosyncrasies with Emacs core

Hello, Kévin Le Gouguec writes: > Nicolas Goaziou writes: > >> For example, having RET >> inserting a plain newline would be a disaster in many locations. > > I don't think I've seen anybody advocating for that!

Re: Parentheses in section titles interfere with on-screen font choice

this > deliberate? And if so, is there a way to put parentheses into section > titles without interfering with the display font? I cannot reproduce it. Is there something in your config? Regards, -- Nicolas Goaziou

Re: 28.0.50; [bug] Inside help buffers escaped symbol[s] causing a problem.

Why would Info buffer display "\`" when you write "`"? I suggest to report it to Emacs developers. Meanwhile, I pushed a work around. Thank you. Regards, -- Nicolas Goaziou

Re: wip-cite status question and feedback

Hello, "Bruce D'Arcus" writes: > On Sat, Apr 25, 2020 at 12:20 PM Nicolas Goaziou > wrote: > [...] >> >> [cite/text: ...] >> [cite/paren: ...] >> > So in this approach, we have a single core "cite" command, and > everyth

Re: wip-cite status question and feedback

le "style-file.csl" :back-ends nil)) where more specialized back-ends are used first. Note that `latex' would mean `latex' and derived back-ends, e.g., `beamer'. Well, that's all for now. Again, I am not a citation specialist, so I need feedback. Let's keep the ball rolling! Regards, -- Nicolas Goaziou

Re: org-set-tags function will overwrite original tags when use it pragmatically

mprove to suitable for this purpose. What about > and > optional argument of this function to decide overwrite or append > method? I think (org-set-tags (cons "LOG" (org-get-tags nil t))) is enough. No need to add arguments. Regards, -- Nicolas Goaziou

Re: small patch for ox-bibtex.el in contrib

small patch (hopefully) > generalizes the search regex. > > I've done only some simple testing but seems to work for my > configuration. Thank you. I eventually pushed a different fix as I noticed other issues in the code. Could you confirm it still solves your problem? Regards, -- Nicolas Goaziou

Re: [RFC] DOCT: Declarative Org Capture Templates

dependently on your new syntax. I invite you to propose a patch for `org-capture-place-entry' so it does a better job at fixing the initial template, if needed. I'll gladly apply it. Regards, -- Nicolas Goaziou

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

Anyway, the real fix should come from Emacs itself. There are ways to make overlays faster. These ways have already been discussed on the Emacs devel mailing list, but no one implemented them. It is a bit sad that we have to find workarounds for that. Regards, -- Nicolas Goaziou

Re: Policy proposal: Do not move existing functions/macros except in major version increments

> That is a good idea, and one that needs addressing. I'd be glad to give > some feedback on it, but in a separate thread, please, because it seems > like a different matter from the issue I'm raising and the proposal I'm > making. I thought most third-party breakages cam

Re: babel/noweb concatenation of equally-named code blocks fails?

Hello, Greg Minshall writes: > below is a format-patch. i signed FSF papers for emacs a number of > years ago (and for gawk more recently). Perfect. I applied it. Thank you! Regards, -- Nicolas Goaziou

Re: Bug: Linking to plain text [9.3.6 (release_9.3.6-471-g9e385d @ c:/Users/awu/.emacs.d/straight/build/org-plus-contrib/)]

gs. In this case, it seems to be the correct behaviour: see variable `org-link-context-for-files' for an explanation and a solution. WDYT? -- Nicolas Goaziou

Re: babel/noweb concatenation of equally-named code blocks fails?

Greg Minshall writes: > two minor edits i might make to the first paragraph, 1) to make clear > that #+name: names only one block, and 2) to (maybe?) simplify the > latter part of the same paragraph, while, at the same time, trying to > keep a strong mention of the distinction between =NAME= and

Re: bug? org-lint issues warning when ; PROPERTIES: drawer before first headline

g-lint be modified? True. Fixed. Thank you. Regards, -- Nicolas Goaziou

Re: babel/noweb concatenation of equally-named code blocks fails?

Hello, Greg Minshall writes: > Nicolas, > > thank you. wordsmithing opens up endless possibilities, so i don't know > that the following is at all an improvement on your suggestion. but, it > occurs to me to get the importance of =noweb-ref=, and its role in > concatena

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

r keywords so to not have this > function signature problem if someone else comes up with a reason to > introduce yet more data. Beware the over-engineering. At this point, someone motivated enough can put an advice to the link fontification function. Regards, -- Nicolas Goaziou

Re: adding paragraph folding to visibility cycling?

ng mechanism. Or maybe the global cycling should be configurable, e.g., as a list of symbols that can be expanded with TAB. It could be complicated to handle intermediate steps, as explained above. As a data point, I wouldn't like to have to hit TAB five times before returning to the ori

Re: [PATCH] Re: Inconsistent use of \ref and \eqref in ox-latex and ox-html

Hello, Brian Powell writes: > Thanks again. Please find attached patch addressing issues below. Perfect. Applied. Thank you! I forgot to add TINYCHANGE at the end of the commit message, but I added you to the list of contributors. Regards, -- Nicolas Goaziou

Re: Faces and spaces

just :CREATED: aligned would be an improvement. I pushed a fix on master for that. Please give it a try if you can. Regards, -- Nicolas Goaziou

Re: Adding Romanian translation for ox.el

#x27;m using a website generated from ox-hugo, that > uses ox.el, this is useful for me and I hope others can find it > helpful in the future. Thank you! I reworded the commit message, added a TINYCHANGE cookie at its end and applied your patch. Regards, -- Nicolas Goaziou

Re: [PATCH] Re: Inconsistent use of \ref and \eqref in ox-latex and ox-html

Hello, Brian Powell writes: > Nicolas, thank you for the feedback, and I apologize for my errors. No need to apologize! Peer review is about catching the mistakes we all do. > I have corrected the issues below and generated a commit patch attached. > Please let me know if ther

Re: issue indent src block?

27;begin'. > And if I move them by hand and them hit C-x h and Tab, they are placed > again as in the example above. I cannot reproduce it. You may want to check if something is setting `org-edit-src-content-indentation' to 0, e.g., .dir-locals.el or some such. Regards, -- Nicolas Goaziou

Re: babel/noweb concatenation of equally-named code blocks fails?

Hello, Greg Minshall writes: > thanks for the history! sounds like a good tradeoff. i agree, a bit > more documentation would be good. I sligthly reworded Noweb references section in the manual. Please let me know if that is clearer. Regards, -- Nicolas Goaziou

Re: babel/noweb concatenation of equally-named code blocks fails?

Greg Minshall writes: > Nicolas, thanks. i take it this is a change from (recent?) past > behavior? I think this was done between Org 9.1 and 9.2, the final step probably being 99dbca3d4f2fb30f35309a0bf4c324535b7dc9f3 > it was kind of nice the old way, but i suspect i'll get

Re: babel/noweb concatenation of equally-named code blocks fails?

> concatenated together to form the replacement text. Yes this part of the manual is not particularly clear, I'll try to reformulate it. Anyway, names are assumed to be unique throughout a document. If you want to concatenate multiple blocks, you need to use :noweb-ref. HTH, -- Nicolas Goaziou

bug#38855: bug#38856: Odp: 26.3; org-clock-display displays 0 total time when the date is in 2020

Hello, Roberto Alejandro Rodriguez writes: > oh thanks for the tip You're welcome. I'm closing these bug reports. Regards, -- Nicolas Goaziou

Re: Inconsistent use of \ref and \eqref in ox-latex and ox-html

ut this variable, using a link filter, e.g. (untested): (defun my-html-filter-references (text backend info) "Change \eqref{...} into \ref{...}." (when (org-export-derived-backend-p backend 'html) (replace-regexp-in-string "\\`eqref{" "ref{" text))) (add-to-list 'org-export-filter-link-functions 'my-html-filter-references) Anyway, would you mind sending an updated patch? Regards, -- Nicolas Goaziou

Re: [SOLVED] Re: [PATCH] Show hidden drawers when org-cycle on headlines

seful. However, Org provides tooling to read and write it, and even display it (e.g., Org Colview) without having to expand them. You may want to expand them to edit them, or simply retrieve information, it is all text after all, but that's not the intended use case, so there is no incentive to expand them automatically. Regards, -- Nicolas Goaziou

Re: [SOLVED] Re: [PATCH] Show hidden drawers when org-cycle on headlines

be: "don't mess with folding state" for regular drawers and blocks, i.e., what is open stays open, what is closed stays closed. But that's more difficult to achieve. Any taker? In any case, I think property drawers need to be "mostly folded". Regards, -- Nicolas Goaziou

Re: Bug: org-publish-sitemap messes absolute sitemap paths [9.3.6 (9.3.6-25-g685b2c-elpa @ c:/Users/juanj/OneDrive/Library/Emacs/elpa-26/org-20200316/)]

> root)) Fixed. Thank you. Regards, -- Nicolas Goaziou

Re: adding paragraph folding to visibility cycling?

es like > origami (say with origami-toggle-all-nodes), but I was wondering if > there's a way to easily add it to org visibility cycling? How would that work? I.e., - what key, - how does it integrate with folding cycling, if it does at all? Regards, -- Nicolas Goaziou

Re: Inconsistent use of \ref and \eqref in ox-latex and ox-html

dence between :html-equation-reference-format is set in back-end definition. Also, it needs to be referenced in "HTML specific properties" section of the manual. Would you want to propose a patch ? Regards, -- Nicolas Goaziou

Re: Bug: org-table-insert-column edits formulas wrongly [9.3 (release_9.3 @ /usr/local/Cellar/emacs-plus/HEAD-9d38564/share/emacs/28.0.50/lisp/org/)]

Hello, Marco Wahl writes: > I had a look at the issue and I think I can take over the > implementation. It's not a big deal AFAICS. Thank you. > Where shall the change go? maint (and master) or just to master? I think maint is fine. Regards, -- Nicolas Goaziou

Re: Policy proposal: Do not move existing functions/macros except in major version increments

ough: "org.el" requires some libraries (e.g., "org-key.el", "org-table.el", ...), and some libraries require "org.el" (e.g., "org-capture.el", "org-element.el", ...). I expect "org.el" to be the entry point for the Org package, so loading should happen in one-way only. This would not solve everything, but it would certainly make things smoother for external libraries. WDYT? Regards, -- Nicolas Goaziou

Re: One inconsistency with org-element parsers

first category, where the contents are not meant to be Org syntax. Regards, -- Nicolas Goaziou

Re: [SOLVED] Re: [PATCH] Show hidden drawers when org-cycle on headlines

. It makes sense if point is on the drawer, and Org does this already. If point is on a headline, possibly a zillion lines above, it doesn't, at least not as a common operation. Regards, -- Nicolas Goaziou

Re: [SOLVED] Re: [PATCH] Show hidden drawers when org-cycle on headlines

property drawers. What is needed, though, it a tooling similar to block visibility functions, i.e., `org-hide-block-toggle', `org-hide-block-hall', and, maybe, `org-hide-block-toggle-maybe'. Regular drawers should get the same treatment as blocks. If you look at `org-cycle

Re: [SOLVED] Re: [PATCH] Show hidden drawers when org-cycle on headlines

ay drawers with `org-cycle', using three prefix arguments. Regards, -- Nicolas Goaziou

Re: links are not parsed in keyword context

s in there. > Could is be possible to parse a link in keyword context? That wouldn't make sense in most contexts. > Alternatively, should I suggest org-ref uses an approach similar to > the one in ~org-return~? I think Org Ref can parse the value of the keyword (a string), instead. There is, for example, `org-element-parse-secondary-string'. Regards, -- Nicolas Goaziou

Re: [PATCH] Show hidden drawers when org-cycle on headlines

l' function, you could write a function that expands properties drawers, and add it to `org-cycle-hook'. Regards, -- Nicolas Goaziou

Re: Bug: Org with auto-fill does not insert linebreaks properly [9.3 (release_9.3 @ /snap/emacs/current/usr/share/emacs/27.0.90/lisp/org/)]

e > expected. I don't think this is specific to Org mode. Text mode behaves the same. The prefix for the current paragraph is "---". Regards, -- Nicolas Goaziou

Re: org-rss feed title is concatenation of all post titles? (ECM included)

Stig Brautaset writes: > Doh! Thanks for that. I tried working around this behaviour ~:lines > "1-"~, to skip the included file's #+title line, but that didn't seem to > work either. E.g. like this: > > : #+include: first-post.org :lines "1-" Doesn't "1-" mean the whole document?

Re: wip-cite status question and feedback

Of course, if you're using biblatex or natbib you'll need another > option for that. I think this part is out of Org's scope. Since values between various citation back-ends are probably not compatible, e.g., some may require a file, others a style name, normalization is not useful here. They can use whatever keyword they fancy. Regards, -- Nicolas Goaziou

Re: wip-cite status question and feedback

"Bruce D'Arcus" writes: > In that case, since it was a typo, I would do as pandoc does: treat it > as a string. Do you mean: keep all spaces wherever they may be?

Re: wip-cite status question and feedback

"Bruce D'Arcus" writes: > On Sun, Apr 12, 2020 at 10:02 AM Nicolas Goaziou > wrote: >> Yes, and a "t-styled" citation would be: >> >> [citet:see;@doe2020;@doe2019] >> >> Barring the prefix, the syntax of the citation does not chan

Re: org-rss feed title is concatenation of all post titles? (ECM included)

ted to create a document title. Regards, -- Nicolas Goaziou

Re: wip-cite status question and feedback

> I'm just a little confused here, particularly on the last item. Why > would one set a style per bib file? No idea. The need exists though: This is a natural following step. Does Org

Re: wip-cite status question and feedback

itet:@doe] could be interpreted as AuthorInText by Citeproc, i.e., Doe (2020) but [citep:@doe] could be ignored, and therefore become (Doe, 2020) Of course Biblatex may interpret it differently. Note that the following proposal drops support for [@key1], which I found awkward anyway. WDYT? -- Nicolas Goaziou

Re: patch for org-confluence.el to add menu entry

contrib directory is loaded first. Thank you. However, I meant a commit message using "git format-patch", for proper attribution. Regards, -- Nicolas Goaziou

Re: patch for org-confluence.el to add menu entry

Hello, Richard Kim writes: > I would like to suggest the following patch so that I can easily export > to Confluence wiki format using the usual org-mode export mechanism. Sure. Could you write a proper commit message and send it again? Thank you. Regards, -- Nicolas Goaziou

Re: [PATCH] Show hidden drawers when org-cycle on headlines

Hello, stardiviner writes: > I think the hidden drawers info is useful for users, this should be > shown when org-cycle on headlines. Doesn't this defeat the whole purpose of drawers? What problem do you want to solve? Regards, -- Nicolas Goaziou

<    3   4   5   6   7   8   9   10   11   12   >