Re: [O] Paragraph consisting only of number and full stop disappears in export

On Sunday, 4 Mar 2018 at 14:07, Eric Abrahamsen wrote: > Hi, > > I just discovered that a paragraph disappeared from a subtree I was > exporting, I guess because the paragraph consists of just a number > followed by a full stop, and was interpreted as a list item. I'm > translating subtitles, and

Re: [O] Adding an item to the agenda from the agenda view

On Sunday, 4 Mar 2018 at 23:22, Shérab wrote: > I would like to add an item with the > corresponding date to my agenda file. What would be the most direct / > straightforward / idiomatic way to achieve this, please? try "i d". "i" should be bound to org-agenda-diary-entry. This is the route I

Re: [O] Feature suggestion and code review request: org-babel-cycle-src-block-header

I guess this is a feature of deleting a region with the point in it. This code, for example, does not preserve point. #+BEGIN_SRC emacs-lisp "<>" (save-excursion (let* ((p1 (point)) (p2 (re-search-backward (concat "<" ">"))) (content (buffer-substring-no-properties p1 p2))) (delete-region

Re: [O] Paragraph consisting only of number and full stop disappears in export

i thought that was example that monospaced it.

Re: [O] Paragraph consisting only of number and full stop disappears in export

Samuel Wales writes: > verse block? Maybe, except that puts it into monospaced font, and I'd have to wrap the whole document in a verse block... > On 3/4/18, Eric Abrahamsen wrote: >> Hi, >> >> I just discovered that a paragraph disappeared from

Re: [O] Paragraph consisting only of number and full stop disappears in export

verse block? On 3/4/18, Eric Abrahamsen wrote: > Hi, > > I just discovered that a paragraph disappeared from a subtree I was > exporting, I guess because the paragraph consists of just a number > followed by a full stop, and was interpreted as a list item. I'm >

Re: [O] Patch for documentation standards

Aloha Bastien, Bastien Guerry writes: Hi Thomas, Feel free to cmmit when appropriate. IMO, the comment period for Nicolas' manual project has been sufficiently long and I do not want to work with you to prolong it. Mhh... "working with me" would shorten it for sure! Anyway, I committed

[O] Paragraph consisting only of number and full stop disappears in export

Hi, I just discovered that a paragraph disappeared from a subtree I was exporting, I guess because the paragraph consists of just a number followed by a full stop, and was interpreted as a list item. I'm translating subtitles, and the dialogue went: #+begin_src org There are no taxis, but I've

Re: [O] Feature suggestion and code review request: org-babel-cycle-src-block-header

John Kitchin writes: > Thanks for the examples. > > There is an interesting issue, the following does not save-excursion! > > (save-excursion > (org-dp-rewire 'src-block t t ;cont ins > t ;aff > nil ;elem > :parameters ":results output")) > > The point gets moved. Do you

Re: [O] [FYI] Programming with org-dp (by example)

Thorsten Jolitz writes: PS Ups ... a few little bugs in the code, here is version 2 #+BEGIN_SRC emacs-lisp (defconst tj/radio-rgxp "^#\\+attr_org:[[:space:]]+:radio") (defconst tj/radio-temp "temp") (defconst tj/radio-wind "wind") (defvar tj/radio-rw '("temp" "wind"))

[O] [FYI] Programming with org-dp (by example)

Hello List, due to some interest in org-dp recently on this list, I actually took the challenge of implementing a feature request by John Kitchin (without actually sticking close to the specification, this is just a showcase for org-dp). Task: implement a radio-list with org checkboxes Extra

Re: [O] Feature suggestion and code review request: org-babel-cycle-src-block-header

Thanks for the examples. There is an interesting issue, the following does not save-excursion! (save-excursion (org-dp-rewire 'src-block t t ;cont ins t ;aff nil ;elem :parameters ":results output")) The point gets moved. Do you know why that happens? John

[O] Adding an item to the agenda from the agenda view

Dear org-mode friends, I use currently only one agenda file. Sometimes, when I need to plan for something, I check the agenda views to find a day when I am available to do that thing. Once I have found this day in the view, I would like to add an item with the corresponding date to my agenda

Re: [O] Patch for documentation standards

Aloha Bastien, > Can you make separate patches, one fixing errors and another one > for the move to editing the manual with .org? > I don't want to commit anything premature. Feel free to cmmit when appropriate. IMO, the comment period for Nicolas' manual project has been sufficiently long

Re: [O] Patch for documentation standards

Hi Thomas, > Feel free to cmmit when appropriate. IMO, the comment period for > Nicolas' manual project has been sufficiently long and I do not want > to work with you to prolong it. Mhh... "working with me" would shorten it for sure! Anyway, I committed this:

Re: [O] [BUG] org-clock-update-mode-line leaves link markup in mode-line

Hi Matt, Matt Lundin writes: > Is this change intentional? It is, of course, possible to strip the link > markup with a custom org-clock-heading-function. But it seems to me that > removing link markup from the mode-line display should remain the > default behavior. Thanks

[O] [BUG] org-clock-update-mode-line leaves link markup in mode-line

Commit 6655429b8d7ee686a8300b61af587599cd656a22 removed code that stripped link markup from the string displayed in the mode line. In the past, a heading like the following... * TODO [[https://en.wikipedia.org/wiki/Org-mode][Org-mode]] ...would be simplified for display in the mode line as...

[O] org-babel-execute-src-block does not insert inline image with `master` branch source code Org

With following example: ``` #+begin_src gnuplot :session :results graphics :file "data/images/sin.png" :cache no set term png set grid plot sin(x), cos(x) #+end_src ``` If I use Org-mode ELPA version. then it works fine. But when I use `master` branch version, then it does not have any result.

Re: [O] [RFC] Moving "manual.org" into core

Hi Nicolas, Nicolas Goaziou writes: >> Is the current contrib/orgmanual.org in sync with doc/org.texi in both >> master and maint? > > Not at all. It is in sync (and a bit above) in master only. Okay. >> How difficult is it to keep it in sync in both branches? > >

Re: [O] [RFC] Moving "manual.org" into core

Hi Nicolas, Nicolas Goaziou writes: > For the record, and as a first feedback, I totally disagree with the > FUD (".org flexibility will bring us new problems", seriously) > spread about the Org manual. Maybe I used the wrong word: let's call them "challenges", not

Re: [O] [RFC] Moving "manual.org" into core

Hello, Bastien Guerry writes: > Is the current contrib/orgmanual.org in sync with doc/org.texi in both > master and maint? Not at all. It is in sync (and a bit above) in master only. > How difficult is it to keep it in sync in both branches? "manual.org" relies on improvements

Re: [O] [RFC] Moving "manual.org" into core

Hi Nicolas, Nicolas Goaziou writes: > "manual.org" was updated a month ago, and, so far, nobody complained > about it. So, I think it's a good time to discuss about what could be > done next. Is the current contrib/orgmanual.org in sync with doc/org.texi in both master

Re: [O] [RFC] Moving "manual.org" into core

Hi Glenn, Glenn Morris writes: > Maybe I'm worried about nothing, but I do suggest asking on emacs-devel. Thanks for your feedback. You are definitely not worried about nothing. I share some of your worries. To speak the truth, I first thought migrating to org as the preferred

Re: [O] Broken worg link

Hi Alex, Alex Branham writes: > https://orgmode.org/worg/org-tutorials/org-google-sync.html > > the link ical2org.awk 404s for me. It should work now, thanks for reporting this. -- Bastien

Re: [O] Broken Worg link

Hi Thomas, "Thomas S. Dye" writes: > https://orgmode.org/worg/org-contrib/babel/languages.html 404s here. thanks a lot for reporting this -- it took me a while, but it was a problem in the nginx configuration. Also, if anyone notices pages with wrong CSS-styling, it probably

Re: [O] Patch for documentation standards

Hi Thomas, "Thomas S. Dye" writes: > A lightly edited and augmented version of the Org documentation > standards is attached. thanks a lot -- if I understand correctly, the patch fixes current errors and also relies on the idea that the manual is written in org (which is not