Re: [O] Possible BUG : table.el tables export incotrrectly

Dear Nicolas, Thanks for the clarification. I misread the documentation. Sorry for the noise... -- Emmanuel Charpentier Le samedi 04 mai 2019 à 23:00 +0200, Nicolas Goaziou a écrit : > Hello, > > Emmanuel Charpentier writes: > > > Org-mode tables do export with their #+caption: and a

Re: [O] Possible BUG : table.el tables export incotrrectly

Hello, Emmanuel Charpentier writes: > Org-mode tables do export with their #+caption: and a usable #+name:, > whereas table.el tables export their content but ignore #+name:, > > #+caption: and #+latex_attr:. Org mode does /not/ handle table.el tables. It merely recognizes them, and send them

[O] Possible BUG : table.el tables export incotrrectly

Org-mode tables do export with their #+caption: and a usable #+name:, whereas table.el tables export their content but ignore #+name:, #+caption: and #+latex_attr:. Minimal (non-)working example : = # tables.el tables ?

Re: [O] Possible bug (?): :noweb doesn't respect indentations (at least i R/BUGS/JAGS).

Thanks ! Ths switch excaped my attention, probably because it is buried in a "literal example" section, which I didn't connect to noweb care and feeding... Maybe the "noweb" section might benefit of a discrete recall of relevant switches ? Thanks again ! -- Emmanuel Charpentier Le mardi 09

Re: [O] Possible bug (?): :noweb doesn't respect indentations (at least i R/BUGS/JAGS).

> On Apr 8, 2019, at 4:01 PM, Emmanuel Charpentier > wrote: > > Compare this org source: > > === > # A small :noweb mystery: indentation > > #+property: header-args:R :session > #+options: toc:nil > #+author: > #+date: > >

[O] Possible bug (?): :noweb doesn't respect indentations (at least i R/BUGS/JAGS).

Compare this org source: === # A small :noweb mystery: indentation #+property: header-args:R :session #+options: toc:nil #+author: #+date: The structure of a probablity proble can be represented by a ~JAGS~ code snippet: #+name:

Re: [O] Possible bug fontifying the terms in numbered description list

Hello, Nick Dokos writes: > Terms in description lists > > - Term :: definition > > are given an `org-list-dt' face, but the regex (org.el: l.6307 or > thereabouts) does not seem to apply to numbered description lists - in: > > 1. Term :: definition > > the Term is given no face at all: is

[O] Possible bug fontifying the terms in numbered description list

Terms in description lists - Term :: definition are given an `org-list-dt' face, but the regex (org.el: l.6307 or thereabouts) does not seem to apply to numbered description lists - in: 1. Term :: definition the Term is given no face at all: is that intentional? Version: Org mode version

Re: [O] Possible bug(s) in MathML handling in ODT export

Sorry for the noise : the bugs do exist, but my previous analysis was false (one paren too much). More data points : * I installed also MathToWeb, and configured it in emacs (via file-local-variables), with the same problematic result. * The error message "LaTeX to MathML converter not

[O] Possible bug(s) in MathML handling in ODT export

Dear list, I have a couple of gripes about LaTeX handling in ODT export when one needs MathML conversion, and therefore a couple of questions: The first one is possibly a gripe with the ox-pandoc exporters. The doc (info manual) states : "Add this line to the Org file. This option is activated

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Hello, emanuel.charpent...@gmail.com writes: > Please find enclosed a proposed patch (against master) to document the > need for babel/polyglossia in order to honor #+language in LaTeX > export. I applied your patch with slight modifications. Thank you. > This is purely a documentation patch.

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Rights transferred to FSF (scanned signed copy of the form set to ass...@fsf.org). HTH, -- Emmanuel Charpentier Le dim. 2 déc. 2018 à 21:26, a écrit : > Dear all, > > Please find enclosed a proposed patch (against master) to document the > need for babel/polyglossia in order to honor

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Dear all, Please find enclosed a proposed patch (against master) to document the need for babel/polyglossia in order to honor #+language in LaTeX export. This is purely a documentation patch. A better solution would be to detect the use of a non-default #+language: and act accordingly. Nicolas

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Emmanuel Charpentier writes: > This is *not* *documented* (not even in the `org-latex-packages-alist''s > docstring). I know. I fixed `org-latex-packages-alist''s docstring two days ago. > Also agreed, with the reservation that "invasive" didn't mean the same > thing in the 1980s (when the

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Dear Nicolas, Thanks a lot for bearing with my nitpicking. A couple remarks below Le jeudi 29 novembre 2018 à 15:07 +0100, Nicolas Goaziou a écrit : > Hello, > > emanuel.charpent...@gmail.com writes: > > > AFAICT, polyglossia is to be preferred to babel for use with > > xelatex or > >

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Hello, emanuel.charpent...@gmail.com writes: > AFAICT, polyglossia is to be preferred to babel for use with xelatex or > lualatex. I'll see if this can be accomodated. What I mean is that you can also add compiler dependant packages in `org-latex-packages-alist'. No need to change the default

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

TL;DR : your fix works, but I disagree with the absence od documentation and default. See below : Le mercredi 28 novembre 2018 à 15:06 +0100, Nicolas Goaziou a écrit : > Hello, > > Emmanuel Charpentier writes: > > > Close, but no cigar : > > > > I used the `customize' interface to add it to

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Hello, Emmanuel Charpentier writes: > Close, but no cigar : > > I used the `customize' interface to add it to `org-latex-default- > packages-alist' (because the package to load is compiler-dependent), This has nothing to do with compiler. You can add it to `org-latex-packages-alist'. > which

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Le mercredi 28 novembre 2018 à 00:40 +0100, Nicolas Goaziou a écrit : > emanuel.charpent...@gmail.com writes: > > > Le mardi 27 novembre 2018 à 21:26 +0100, Nicolas Goaziou a écrit : > > > > [ Snip... ] > > > > > What happens if you remove "org-ref.el" reference? > > > > Same thing. > > > >

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

emanuel.charpent...@gmail.com writes: > Le mardi 27 novembre 2018 à 21:26 +0100, Nicolas Goaziou a écrit : > > [ Snip... ] > >> What happens if you remove "org-ref.el" reference? > > Same thing. > > Even after uninstalling org-ref and its dependencies. > > Sorry... OK. I got it. This has nothing

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Le mardi 27 novembre 2018 à 21:26 +0100, Nicolas Goaziou a écrit : [ Snip... ] > What happens if you remove "org-ref.el" reference? Same thing. Even after uninstalling org-ref and its dependencies. Sorry... -- Emmanuel Charpentier

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Hello, Emmanuel Charpentier writes: > My original posting included the tex file generated by C-c C-e l l. > Perusing it will show you that babel is not used anywhere in this export. > > On the (remote) chance that my problem might be caused by my use of emacs > 25.2, I just installe emacs 26

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

My original posting included the tex file generated by C-c C-e l l. Perusing it will show you that babel is not used anywhere in this export. On the (remote) chance that my problem might be caused by my use of emacs 25.2, I just installe emacs 26 from the emacs-snapshot packages for Debian

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Hello, Emmanuel Charpentier writes: > As of today, I note that the #+langiage export variable is no longer > honored when exporting to LaTeX/PDF. See enclosed files : I noticed this quite some time go (months, last year maybe), but didn't dived into it because I'm not sure what to expect.

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

On Sunday, 25 Nov 2018 at 21:36, emanuel.charpent...@gmail.com wrote: > I forgot to add that, when exporting to plain tex or ODT, #+language* > *seems* to be honored : the table of contents is entitled "Table des > matières". > > The problem is therefore probably in ox-latex.el (but way above my >

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

I forgot to add that, when exporting to plain tex or ODT, #+language* *seems* to be honored : the table of contents is entitled "Table des matières". The problem is therefore probably in ox-latex.el (but way above my level of competance in em... -- Emmanuel Charpentier

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

I forgot to add that, when exporting to plain tex or ODT, #+language* *seems* to be honored : the table of contents is entitled "Table des matières". The problem is therefore probably in ox-latex.el (but way above my level of competance in emacs-lisp...). -- Emmanuel Charpentier

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Hello, Emmanuel Charpentier writes: > I have but one *visual* clue : whereas the fontlock gives me a gray > color for #+title, #+author and #+date (light gray for the tags, dark > blue for the title, medium grey for author and date), "#+language: fr" > remains in red, even after C-c C-c.

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Yet another data point: I followed your suggestion : * desinstalled MELPA's org * cloned https://code.orgmode.org/bzg/org-mode.git * make autoloads * make * emacs -q * M-: (add-to-list 'load-path "/org-mode/lisp") C-c C-e l o still gets me the same result (i. e. a table of contents

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Emmanuel Charpentier writes: > Thanks for a prompt answer ! A couple questions : > > 1) What do you mean by "minimal configuration" ? A stripped > .emacs/d/init.el ? Indeed. > 2) How can I get the "development version" ? I'm following MELPA > already... You have to clone the repository and

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

One more data point : I can reproduce the problem with no init file : * same org file * emacs started by "emacs -q" * M-x (require 'org) * C-x C-f TstLanguage.org * C-c C-e l p ==> Same result. HTH, -- Emmanuel Charpentier Le dimanche 25 novembre 2018 à 20:03 +0100, Nicolas Goaziou

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Thanks for a prompt answer ! A couple questions : 1) What do you mean by "minimal configuration" ? A stripped .emacs/d/init.el ? 2) How can I get the "development version" ? I'm following MELPA already... -- Emmanuel Charpentier Le dimanche 25 novembre 2018 à 20:03 +0100, Nicolas Goaziou a

Re: [O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

Hello, Emmanuel Charpentier writes: > As of today, I note that the #+langiage export variable is no longer > honored when exporting to LaTeX/PDF. See enclosed files : > > - #+language:fr should get me a table of contents entitled "Table des > matières" ; > > - #+ the Latex file has

[O] Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.

As of today, I note that the #+langiage export variable is no longer honored when exporting to LaTeX/PDF. See enclosed files : - #+language:fr should get me a table of contents entitled "Table des matières" ; - #+ the Latex file has "pdflang={Frenchb}}" in a \hypersetup call, but nothing

Re: [O] Possible bug with coderef highlighting in HTML export

Hello, Thibault Marin writes: > Hi the attach patch fixes the issue for me. Please let me know if you > have any suggestions. It looks good. Applied. Thank you. Regards, -- Nicolas Goaziou

Re: [O] Possible bug with coderef highlighting in HTML export

Hi, Hi the attach patch fixes the issue for me. Please let me know if you have any suggestions. As always, thanks for the guidance. thibault >From a78dc91c9fd1aacb2c65f66ae5afa9ee25f56e01 Mon Sep 17 00:00:00 2001 From: thibault Date: Sun, 3 Dec 2017 17:42:13 -0600

Re: [O] Possible bug with coderef highlighting in HTML export

Hello, Thibault Marin writes: > I am using Org mode version 9.1.3 (release_9.1.3-216-g259656 @ > /.../org-mode/lisp/) and I am experiencing an issue with the exported > HTML of the following org file: > > , > | this links get highlighted [[(link0)]]. > | > | this

[O] Possible bug with coderef highlighting in HTML export

Hi all, I am using Org mode version 9.1.3 (release_9.1.3-216-g259656 @ /.../org-mode/lisp/) and I am experiencing an issue with the exported HTML of the following org file: , | this links get highlighted [[(link0)]]. | | this link does not get highlighted [[(link1)]]. | | #+begin_src

Re: [O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

Hello, swfl...@flintfam.org (Samuel W. Flint) writes: > Hey -- I'm at Org mode version 9.1.3 (release_9.1.3-185-g579fa1 @ > /home/swflint/.emacs.d/org-mode/lisp/), and GNU Emacs 25.2.1 > (x86_64-unknown-linux-gnu, GTK+ Version 3.22.18) of 2017-08-29, and on > my files with level 3 headings and

Re: [O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

Yes, I have same issue too. - [ ] org-indent-mode display the 3rd level asterisk as bold - [ ] I can't =[C-c C-f]= And confirmed it is caused by commit ed06b159c | * Small fix to emphasis fontification. [stardiviner] GPG key ID: 47C32433 IRC(freeenode): stardiviner

Re: [O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

"Samuel W. Flint" writes: >> Samuel W Flint writes: > >> Kyle Meyer writes: > KM> "Samuel W. Flint" writes: > >>> Any idea what might be causing this? I checked > >>> org-bullets-mode, but that doesn't seem to be it. > > KM>

Re: [O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

> Samuel W Flint writes: > Kyle Meyer writes: KM> "Samuel W. Flint" writes: >>> Any idea what might be causing this? I checked >>> org-bullets-mode, but that doesn't seem to be it. KM> No, sorry. Hopefully others might have a hunch. I'd suggest

Re: [O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

> Kyle Meyer writes: KM> "Samuel W. Flint" writes: >> Any idea what might be causing this? I checked org-bullets-mode, >> but that doesn't seem to be it. KM> No, sorry. Hopefully others might have a hunch. I'd suggest KM> that you first verify

Re: [O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

"Samuel W. Flint" writes: > Any idea what might be causing this? I checked org-bullets-mode, but > that doesn't seem to be it. No, sorry. Hopefully others might have a hunch. I'd suggest that you first verify that you don't see the issue when you use Org without your

Re: [O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

> Kyle Meyer writes: First, sorry about accidentally sending nearly the same email twice. KM> "Samuel W. Flint" writes: >> Hey -- I'm at Org mode version 9.1.3 (release_9.1.3-185-g579fa1 @ >> /home/swflint/.emacs.d/org-mode/lisp/), and GNU Emacs 25.2.1

Re: [O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

"Samuel W. Flint" writes: > Hey -- I'm at Org mode version 9.1.3 (release_9.1.3-185-g579fa1 @ > /home/swflint/.emacs.d/org-mode/lisp/), and GNU Emacs 25.2.1 > (x86_64-unknown-linux-gnu, GTK+ Version 3.22.18) of 2017-08-29, and on > my files with level 3 headings and

[O] Possible bug: Headings greater than level 2 stars not showing -- unable to navigate with normal commands

Hey -- I'm at Org mode version 9.1.3 (release_9.1.3-185-g579fa1 @ /home/swflint/.emacs.d/org-mode/lisp/), and GNU Emacs 25.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.22.18) of 2017-08-29, and on my files with level 3 headings and greater, the stars aren't showing, and I'm unable to use the

Re: [O] possible bug exporting blocks?

thanks! John --- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu On Fri, May 19, 2017 at 10:30 AM, Nicolas Goaziou

Re: [O] possible bug exporting blocks?

Hello, John Kitchin writes: > If I export this block to org (C-c C-e O O): > > #+begin: exercise > #+ipynb-newcell > > *Exercise 1* #+end > > I get this: > > #+BEGIN: exercisenil > #+ipynb-newcell > > *Exercise 1* > #+END: > > there is an extra nil at the end of the

[O] possible bug exporting blocks?

If I export this block to org (C-c C-e O O): #+begin: exercise #+ipynb-newcell *Exercise 1* #+end I get this: #+BEGIN: exercisenil #+ipynb-newcell *Exercise 1* #+END: there is an extra nil at the end of the first line. That seems like a bug, does anyone else get this? I am running org 9.0.5.

Re: [O] Possible Bug in Capture.

> > Your template is invalid. Per `org-capture-templates', it should be > > (file+datetree "path/to/file") > > IOW, there should be no "Notes." > > > Regards, > > -- > Nicolas Goaziou > Thank you! Things have obviously changed since the last time I set up a capture template. Note to self:

Re: [O] Possible Bug in Capture.

Hello, li...@wilkesley.net writes: > I have just switched from maint to master and now get the following > error capturing to a date tree: > > #+begin_src emacs-lisp > Debugger entered--Lisp error: (error "Invalid capture target > specification: (file+datetree >

[O] Possible Bug in Capture.

I have just switched from maint to master and now get the following error capturing to a date tree: #+begin_src emacs-lisp Debugger entered--Lisp error: (error "Invalid capture target specification: (file+datetree \"~/Documents/emacs/org/org_files/tasks/notes.org\" \"Notes.\")")

Re: [O] Possible bug: Emacs hangs on (require 'org)

Hi! About every third time I start Emacs, I also experience a very slow startup with org-mode 9.0.3 enabled. I run "GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 2016-04-17 on lgw01-04, modified by Debian" on Linux Mint 18.1 Cinnamon. Here is my minimal setup: ;;;

Re: [O] Possible bug: Emacs hangs on (require 'org)

Luke writes: > On 23/11/16 10:39, Eric Abrahamsen wrote: >> Luke writes: [...] >>> I tried creating a minimal-org.el file with the following contents: >>> >>> ;; activate debugging >>> (setq debug-on-error t >>>

Re: [O] Possible bug: Emacs hangs on (require 'org)

On 23/11/16 10:39, Eric Abrahamsen wrote: Luke writes: I have a strange situation on my laptop. I'm running Ubuntu 16.04, with Emacs 24.5.1. I'm also using the latest development branch from the org-mode git repository (latest changes pulled today). Recently,

Re: [O] Possible bug: Emacs hangs on (require 'org)

On 23/11/16 09:31, Luke wrote: I have a strange situation on my laptop. I'm running Ubuntu 16.04, with Emacs 24.5.1. I'm also using the latest development branch from the org-mode git repository (latest changes pulled today). Recently, for some unknown reason, emacs suddenly started to hang on

Re: [O] Possible bug: Emacs hangs on (require 'org)

Luke writes: > I have a strange situation on my laptop. > > I'm running Ubuntu 16.04, with Emacs 24.5.1. I'm also using the latest > development branch from the org-mode git repository (latest changes > pulled today). > > Recently, for some unknown reason, emacs

[O] Possible bug: Emacs hangs on (require 'org)

I have a strange situation on my laptop. I'm running Ubuntu 16.04, with Emacs 24.5.1. I'm also using the latest development branch from the org-mode git repository (latest changes pulled today). Recently, for some unknown reason, emacs suddenly started to hang on startup. Placing some

Re: [O] Possible bug on ob-python.el

Ignore this, I misunderstood some things and it works ok now. On Thu, Sep 29, 2016 at 11:47:13PM +0200, drymer wrote: Hi, I'm not sure if it's a bug or if it's something I have missconfigured, but there it goes. I'm using maint Org-mode version 8.3.6, release_8.3.6-4-g4835be.dirty. The init

[O] Possible bug on ob-python.el

Hi, I'm not sure if it's a bug or if it's something I have missconfigured, but there it goes. I'm using maint Org-mode version 8.3.6, release_8.3.6-4-g4835be.dirty. The init file I'm using to debug is: #+BEGIN_SRC emacs-lisp (add-to-list 'load-path "~/.emacs.d/lisp/org-mode/lisp/")

Re: [O] Possible bug in LaTeX export of special blocks

Aloha Nicolas, Nicolas Goaziou writes: >> >> The blank line after \label{orgspecialblock1} causes the equation number >> to be set on the following line, rather than to the right of the >> equation. My expectation is there is no blank line after the \label, >> which yields the desired behavior.

Re: [O] Possible bug in LaTeX export of special blocks

Hello, Thomas S. Dye writes: > Exporting these two special blocks to LaTeX > > ,-- > | #+name: eq:foobar > | #+begin_equation > | foo = bar > | #+end_equation > | > | #+begin_equation > | bar = baz > | #+end_equation >

[O] Possible bug in LaTeX export of special blocks

Aloha all, Exporting these two special blocks to LaTeX ,-- | #+name: eq:foobar | #+begin_equation | foo = bar | #+end_equation | | #+begin_equation | bar = baz | #+end_equation `-- yields this in the tex file

Re: [O] Possible bug: Can not search for text in links - only description

On 2015-03-20 at 13:53, Samuel Wales samolog...@gmail.com wrote: hmm: === search-invisible is a variable defined in `isearch.el'. Its value is open Documentation: If t incremental search/query-replace can match hidden text. A nil value means don't match invisible text. When the value is

Re: [O] Possible bug: Can not search for text in links - only description

hi ken, that's right, my point was that perhaps it is relevant, not that one would set the variable. for example, perhaps there is a way that timestamps can have an invisible property and thus be subject to this variable. of course, it might not be possible, if timestamps do not use overlays,

Re: [O] Possible bug: Can not search for text in links - only description

Charles C. Berry ccbe...@ucsd.edu writes: On Fri, 20 Mar 2015, Ken Mankoff wrote: It would be nice to be able to search in links without extra work to change modes. Without this, you cannot even search for a cite key! You *can* search in links without changing modes. menu-bar edit search

Re: [O] Possible bug: Can not search for text in links - only description

Thanks everybody - many useful comments and ideas. First I must say it makes sense to give the error message, although I was quite surprised. But the message should contain a string one can easily search for. And I guess the most used search function is C-s I think the message should be changes

Re: [O] Possible bug: Can not search for text in links - only description

On Mon, Mar 23, 2015 at 8:45 AM, Rainer M Krug rai...@krugs.de wrote: First I must say it makes sense to give the error message, although I was quite surprised. But the message should contain a string one can easily search for. And I guess the most used search function is C-s I think the

Re: [O] Possible bug: Can not search for text in links - only description

Jacob Gerlach jacobgerl...@gmail.com writes: On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug rai...@krugs.de wrote: Hi I got an error as follow when I tried to export: , | org-babel-exp process R at line 5495... | Evaluation of this R code-block is disabled. | user-error: Unable to

Re: [O] Possible bug: Can not search for text in links - only description

Rainer M Krug Rainer at krugs.de writes: M-x occur RET Exa RET Ah - occur is nice - very nice. I like the output and also that it shows me all hits - I'll use this more often! It even has a key binding: M-s o. If you like a function and wonder if it has a key binding: C-h w function name

Re: [O] Possible bug: Can not search for text in links - only description

Achim Gratz strom...@nexgo.de writes: Rainer M Krug Rainer at krugs.de writes: M-x occur RET Exa RET Ah - occur is nice - very nice. I like the output and also that it shows me all hits - I'll use this more often! It even has a key binding: M-s o. If you like a function and wonder if it

Re: [O] Possible bug: Can not search for text in links - only description

On 2015-03-21T01:59:07+1100, Richard Lawrence richard.lawre...@berkeley.edu said: RL I am not sure if this counts as a bug or not, so someone else RL should still address this question. Maybe this is the desired RL behavior, given that the link text is hidden? Or maybe it's just RL not

Re: [O] Possible bug: Can not search for text in links - only description

On Sat, Mar 21, 2015 at 7:34 PM, Alexis flexibe...@gmail.com wrote: On 2015-03-21T01:59:07+1100, Richard Lawrence richard.lawre...@berkeley.edu said: RL I am not sure if this counts as a bug or not, so someone else RL should still address this question. Maybe this is the desired RL

Re: [O] Possible bug: Can not search for text in links - only description

Hi Rainer, In terms of searching through all open buffers, here is what I use (helm and helm-multi-occur): , | (setq helm-M-x-requires-pattern 0) | | ;; http://emacs.stackexchange.com/a/740 | (require 'helm-regexp) | (eval-after-load helm-regexp | '(setq helm-source-moccur |

[O] Possible bug: Can not search for text in links - only description

Hi I got an error as follow when I tried to export: , | org-babel-exp process R at line 5495... | Evaluation of this R code-block is disabled. | user-error: Unable to resolve link *uLELFit ` I thought OK - I'll search for uLELFit and just fix this link - but I could do what I wanted, I

Re: [O] Possible bug: Can not search for text in links - only description

Richard Lawrence wrote: Rainer M Krug rai...@krugs.de writes: I figured out that I can not search for text in the link. Thins is quite annoying, especially as I even thought of opening the file in another texteditor, search for the string, and save it again. As an example: if this link is

Re: [O] Possible bug: Can not search for text in links - only description

Hi Rainer, Rainer M Krug rai...@krugs.de writes: I figured out that I can not search for text in the link. Thins is quite annoying, especially as I even thought of opening the file in another texteditor, search for the string, and save it again. As an example: if this link is in an

Re: [O] Possible bug: Can not search for text in links - only description

On Fri, Mar 20, 2015 at 9:44 AM, Rainer M Krug rai...@krugs.de wrote: Hi I got an error as follow when I tried to export: , | org-babel-exp process R at line 5495... | Evaluation of this R code-block is disabled. | user-error: Unable to resolve link *uLELFit ` I thought OK -

Re: [O] Possible bug: Can not search for text in links - only description

hmm: === search-invisible is a variable defined in `isearch.el'. Its value is open Documentation: If t incremental search/query-replace can match hidden text. A nil value means don't match invisible text. When the value is `open', if the text matched is made invisible by an overlay having an

Re: [O] Possible bug: Can not search for text in links - only description

org-show-context-detail may also be relevant: org-show-context-detail is a variable defined in `org.el'. Its value is ((isearch . lineage) (bookmark-jump . lineage) (default . ancestors)) Documentation: Alist between context and visibility span when revealing a location. Some actions may

Re: [O] Possible bug: Can not search for text in links - only description

On Fri, 20 Mar 2015, Ken Mankoff wrote: It would be nice to be able to search in links without extra work to change modes. Without this, you cannot even search for a cite key! You *can* search in links without changing modes. menu-bar edit search search-forward Exa RET runs

Re: [O] Possible bug: Can not search for text in links - only description

It would be nice to be able to search in links without extra work to change modes. Without this, you cannot even search for a cite key! -k. Please excuse brevity. Sent from pocket computer with tiny non-haptic feedback keyboard. On Mar 20, 2015, at 11:38, Jacob Gerlach

[O] Possible bug

I'm not sure if this counts as a bug or not: If I run a custom agenda (eg. R) with sticky agendas, it displays in an buffer with the name *Org Agenda (R)* If this buffer is then renamed to e.g. (rename-buffer *R-Agenda*) *R-Agenda* And is then refreshed by hitting r, the agenda is properly

Re: [O] Possible bug

Hello, Subhan Michael Tindall subh...@familycareinc.org writes: I'm not sure if this counts as a bug or not: If I run a custom agenda (eg. R) with sticky agendas, it displays in an buffer with the name *Org Agenda (R)* If this buffer is then renamed to e.g. (rename-buffer *R-Agenda*)

Re: [O] Possible bug in export of table in latex

Hi, thanks for responding. As a matter of fact, I think the :width option for latex tables should be disabled, because it is not so simple to implement. While it is possible to reduce the width with Eric's trick, it is not so easy to enlarge the width without using the :align option and

Re: [O] Possible bug in export of table in latex

Nicolas Goaziou m...@nicolasgoaziou.fr writes: Hello, Giuseppe Lipari giulip...@gmail.com writes: As a matter of fact, I think the :width option for latex tables should be disabled, because it is not so simple to implement. As long as it doesn't generate invalid LaTeX code (like in your

Re: [O] Possible bug in export of table in latex

Hello, Giuseppe Lipari giulip...@gmail.com writes: As a matter of fact, I think the :width option for latex tables should be disabled, because it is not so simple to implement. As long as it doesn't generate invalid LaTeX code (like in your bug report), I think the current :width option can

[O] Possible bug in export of table in latex

Dear all, happy new year to everybody! I think I might have discovered a bug. I am preparing some slides using org-beamer mode. Here is the snippet of a table I have in my file: #+ATTR_LATEX: :float t :width 4cm | /Single node app/ | /Distributed app/ |

Re: [O] Possible bug in export of table in latex

Hello, Giuseppe Lipari giulip...@gmail.com writes: I am preparing some slides using org-beamer mode. Here is the snippet of a table I have in my file: #+ATTR_LATEX: :float t :width 4cm | /Single node app/ | /Distributed app/ |

Re: [O] Possible bug in export of table in latex

On Tuesday, 6 Jan 2015 at 14:03, Giuseppe Lipari wrote: Dear all, happy new year to everybody! I think I might have discovered a bug. I am preparing some slides using org-beamer mode. Here is the snippet of a table I have in my file: #+ATTR_LATEX: :float t :width 4cm | /Single

[O] Possible bug with Org Babel source code blocks and ESS integration

I am having a strange problem with R Source Blocks. Let me explain (I hope the explanation below makes sense). When I am creating a source block, I typically create the #+BEGIN_SRC and #+END_SRC lines, and then use C-c ' to enter ESS mode, fill the block there, and return to my org buffer

Re: [O] Possible bug with Org Babel source code blocks and ESS integration

Hi Vikas, 2014ko abenudak 11an, Vikas Rawal-ek idatzi zuen: I am having a strange problem with R Source Blocks. Let me explain (I hope the explanation below makes sense). When I am creating a source block, I typically create the #+BEGIN_SRC and #+END_SRC lines, and then use C-c ' to enter

Re: [O] Possible bug with Org Babel source code blocks and ESS integration

I just pushed a change to master (398286a) which should fix this issue, and one other I discovered along the way. These bugs may have been dislodged by Nicolas’s recent rework of this code. (Not that I’m complaining – the new code seems a lot pleasanter, even with a couple transitory bugs.

Re: [O] Possible bug with Org Babel source code blocks and ESS integration

2014ko abenudak 11an, Vikas Rawal-ek idatzi zuen: Yes, it works fine now. Glad to hear it, thanks for confirming. -- Aaron Ecay

[O] possible bug in adding properties to headlines with no properties

I noticed an undesirable behavior in setting a property on a headline with no properties, but which contains a code block that generates headlines with properties. When I try to set a property with C-c C-x p, the property gets put in the wrong place (inside the code block). It is a small issue,

Re: [O] possible bug in adding properties to headlines with no properties

On Fri, 28 Nov 2014, John Kitchin wrote: I noticed an undesirable behavior in setting a property on a headline with no properties, but which contains a code block that generates headlines with properties. When I try to set a property with C-c C-x p, the property gets put in the wrong place

Re: [O] possible bug in adding properties to headlines with no properties

Charles C. Berry ccbe...@ucsd.edu writes: thanks for the note. I am still on 8.2.7, so it sounds like the issue is fixed upstream of me. I look forward to getting there! On Fri, 28 Nov 2014, John Kitchin wrote: I noticed an undesirable behavior in setting a property on a headline with no

Re: [O] Possible bug, installing outshine before outorg

Brady Trainor algeb...@uw.edu writes: Hi, Newb bug report: I think if I have a brand new Emacs setup, installing org with an emacs -q, then installing outshine.el (all with built-in package manager), that there is some problems created, possibly because of outorg to install (IIRC, a

[O] Possible bug, installing outshine before outorg

Newb bug report: I think if I have a brand new Emacs setup, installing org with an emacs -q, then installing outshine.el (all with built-in package manager), that there is some problems created, possibly because of outorg to install (IIRC, a silent-notifications type of problem). If I start

  1   2   >