Re: [O] non-space, paste, (???) character for inline results

Nico, > At some point, someone will want to write foo#call_bar() without > #call_bar() being replaced, and we will go back to point 0. IMO, > zero-width space is the way to go, if only because it can already be > used to escape other special characters in Org. oof, of course! color me

Re: [O] setting flags in python src blocks?

Thanks. That does work for flags the interpreter knows, but python doesn't understand --some_flag (I mean literally that flag!). It turns out I meant: python test.py --some_flag=True. It looks like that is not currently possible. John --- Professor John Kitchin

Re: [O] setting flags in python src blocks?

Hi, On Thu, Feb 1, 2018 at 8:47 AM, John Kitchin wrote: > Is it possible to set command line flags for an executable in src blocks? I > was thinking of something like this > > #+BEGIN_SRC python :flags --some_flag=True :tangle test.py > import app > >

Re: [O] exporting a big project in multiple files to both pdf and html

Hi, On Fri, Jan 26, 2018 at 2:37 AM, Alan Schmitt wrote: > I'm working on a project that is becoming too big to manage as a single > file, so I'm looking at splitting it in several files. This would also > have the benefit of generating several smaller html pages

[O] setting flags in python src blocks?

Is it possible to set command line flags for an executable in src blocks? I was thinking of something like this #+BEGIN_SRC python :flags --some_flag=True :tangle test.py import app print(app.FLAGS.some_flag) # -> True #+END_SRC which would be equivalent to running: > python --some_flag=True

Re: [O] Org-get-property-block can’t handle preceding drawers

Nicolas Goaziou, 2018-01-31 20:12: Nikolai Weibull writes: At first I figured that the rules had changed and that the :PROPERTY: drawer must come first That's correct. but then I tried it out and Org would gladly create a new :LOGBOOK: drawer for an entry that already had

Re: [O] Trivial bug in ox-latex

Hello, Akater writes: > The following snippet in ox-latex.el processes negative tocdepths > incorrectly: > > #+begin_src emacs-lisp > ;; Table of contents. > (let ((depth (plist-get info :with-toc))) > (when depth > (concat (when (wholenump depth) >

Re: [O] Org-get-property-block can’t handle preceding drawers

Hello, Nikolai Weibull writes: > At first I figured that the rules had changed and that > the :PROPERTY: drawer must come first That's correct. > but then I tried it out and Org would gladly create a new :LOGBOOK: > drawer for an entry that already had a :PROPERTY: drawer and

[O] Trivial bug in ox-latex

The following snippet in ox-latex.el processes negative tocdepths incorrectly: #+begin_src emacs-lisp ;; Table of contents. (let ((depth (plist-get info :with-toc))) (when depth (concat (when (wholenump depth) (format "\\setcounter{tocdepth}{%d}\n" depth))

[O] Org-get-property-block can’t handle preceding drawers

Hi! I’m doing some restructuring of my Org files and I’m getting a lot of claims that I have malformed drawers. Some of these files are quite old, so at first this seemed like a reasonable problem, but when I looked closer everything looked fine. The problem was that I had :LOGBOOK:

Re: [O] [RFC] Could we get rid of Org specific "mark ring"

this is ot but another bit of over-fancification is that iirc you can't set the mark twice successively in the same location. you might not think there is a need for that, but there is [marking contiguous regions], but even if there were not, the value of predictable behavior with no special

Re: [O] [RFC] Could we get rid of Org specific "mark ring"

in my usage, the current distinction between org-mark-ring and mark-ring does not disturb me at all. i agree that it would be good to be able to use global-mark-ring as a substitute for both global-mark-ring and org-mark-ring, but ONLY if it takes me to the exact location just like org-mark-ring

Re: [O] non-space, paste, (???) character for inline results

Greg Minshall writes: > ah. how does one enter a zero-width space in emacs/org-mode? also, i'm > curious about how it looks on the screen. (for me, i'd want it to look, > on the screen, *very* obvious that *something* is there.) > > i also apologize that the patch i sent

Re: [O] non-space, paste, (???) character for inline results

On Wed, Jan 31, 2018 at 12:51 PM Kaushal Modi wrote: > > All glyphs are shown in `modi/highlight-confusing' face." > Forgot to paste the face definition (I just set it to colors to suit my default theme): (defface modi/highlight-confusing '((t (:foreground "black"

Re: [O] non-space, paste, (???) character for inline results

On Wed, Jan 31, 2018 at 12:44 PM Greg Minshall wrote: > > ah. how does one enter a zero-width space in emacs/org-mode? By default, you can do C-x 8 RET and type ZERO WIDTH SPACE and the 0x200b character will be inserted. I use it once in a while, so I have bound it to C-x 8

Re: [O] non-space, paste, (???) character for inline results

Nico, > I meant zero-width space, not non-breaking space. Note that it can be > used in other places to escape special characters, e.g., verbatim > markup. ah. how does one enter a zero-width space in emacs/org-mode? also, i'm curious about how it looks on the screen. (for me, i'd want it to

[O] bug#30310: Built-in Org mode not listed as installed package

Package: emacs,org-mode Version: 25.3 emacs -Q -f list-packages The built-in Org mode is not listed. (This eg causes org-edna to be listed as uninstallable.) Adding a Version: header comment to lisp/org/org.el would fix this. (There was one prior to Emacs rev 8223b1d233.) Obviously it would need

Re: [O] non-space, paste, (???) character for inline results

Greg Minshall writes: > thanks. neither =verbatim markup= (if that's the usage), nor a > non~breaking~space give me, in my output, a plain, unadorned > "xxcall_foo()". I meant zero-width space, not non-breaking space. Note that it can be used in other places to escape special

Re: [O] non-space, paste, (???) character for inline results

Nico, thanks. neither =verbatim markup= (if that's the usage), nor a non~breaking~space give me, in my output, a plain, unadorned "xxcall_foo()". i *do* think xxcall_foo() is very intuitive for both sets of people, both those who want xx+results and those who want literal xxcall_foo(). so,

Re: [O] [RFC] Could we get rid of Org specific "mark ring"

Hello, Samuel Wales writes: > On 1/30/18, Allen Li wrote: >> It does change org behavior, since the native mark ring >> distinguishes local from global, whereas org-mark-ring does not. >> With the proposed change, there won't be a single >>

Re: [O] non-space, paste, (???) character for inline results

Hello, Greg Minshall writes: > not wanting to look gift horses, etc., but i've a question. if i > understand the change correctly > > - (looking-at "\\ + (looking-at "call_\\([^ \t\n[(]+\\)[([]")) > > now

Re: [O] executing org-table TBLFM form changes (resets) language settings

Hello, Rainer Stengele writes: > I set the variables in my .emacs: > > (defvar math-short-weekday-names '( "So" "Mo" "Di" "Mi" "Do" "Fr" "Sa" )) Shouldn't it be (setq math-short-weekday-names '("So" ...)) > Very strange, no clue why that happens. No clue either.

Re: [O] executing org-table TBLFM form changes (resets) language settings

Am 30.01.2018 um 22:07 schrieb Nicolas Goaziou: Hello, Rainer Stengele writes: has anybody an idea? Each time I calculate a time diff in an Org table I trigger the wrong creation of any org timestamp as the date language has changed. Full restart of Emacs needed