Re: [O] make test is failing? [ob-fortran stuff]
I always fail the Fortran tests too, on Mac OS X 10.6.8, though supposedly there's a Fortran interpreter in there somewhere. Yours, Christian Kaushal Modi writes: > Hi all, > > I cloned a fresh copy of org-mode and ran "make test" for the first time. > > The following are failing: > > 3 unexpected results: >FAILED ob-fortran/list-matrix-from-table1 >FAILED ob-fortran/list-matrix-from-table2 >FAILED ob-fortran/list-var-from-table > > Is it known? Or it's failing just for me? > > I am running Emacs version: GNU Emacs 25.0.91.1 (x86_64-unknown-linux-gnu, > GTK+ Version 2.24.23) of 2016-02-21, built using commit > e19c1c301700430ae428f40c2a364671f5d50dcf. > > > -- > Kaushal Modi
[O] Cannot export bash src
Hello, I have a strange behaviour when trying to produce a beamer presentation . I have a rather complicated set of slides, one of the slide contains this snippet: %- snippet --% ** CGI - producing output - Example in shell script: #+BEGIN_SRC bash echo "content-type: text/html" echo echo "" echo "" echo "" echo "it is "`date`"" echo "" echo "" #+END_SRC %- snippet --% I use minted for formatting the visual output. When I try to export to beamer, it stops well before the export with the following error: [...] org-babel-exp process emacs-lisp at line 16... org-babel-exp process html at line 114... org-babel-exp process html at line 164... org-babel-exp process bash at line 270... byte-code: Invalid search bound (wrong side of point) If I comment the above snippet, everything is all right, so I think it should be the culprit. However, if I isolate the above snippet in separate org file, the pdf file is produced all right. Anybody has any idea of what is going on? I am available to give you more information (my init.org, and the whole org file, if necessary). Giuseppe Lipari
[O] how to change the resizebox for a generated tikz diagram?
Hello,
When exporting this source block to beamer
#+header: :file (by-backend (beamer "foldleft.tikz") (t "foldleft.png"))
#+header: :imagemagick yes :iminoptions -density 600 :imoutoptions -geometry 800
#+header: :results file raw
#+header: :headers '("\\usepackage{tikz}")
#+begin_src latex
\usetikzlibrary{matrix,arrows}
\begin{tikzpicture}[scale=2, every node/.style={transform shape}]
\matrix (m) [matrix of nodes, row sep=2em, column sep=3em]
{ & $[x_1;$ & $x_2;$ & $\ldots;$ & $x_n]$ & \\
$acc$ & \node (f1) [circle, draw] {$f$}; & \node (f2) [circle,draw] {$f$}; &
& \node (fn) [circle,draw] {$f$}; & \texttt{fold\_left } $f$ \; $acc$ \; $[x_1;
x_2; \ldots; x_n]$\\
};
\draw (m-2-1) edge[->,thick] (f1);
\draw (f1) edge[->,thick] (f2);
\draw (f2) edge[->,thick,dotted] (fn);
\draw (fn) edge[->,thick] (m-2-6);
\draw (m-1-2) edge[->,thick] (f1);
\draw (m-1-3) edge[->,thick] (f2);
\draw (m-1-5) edge[->,thick] (fn);
\end{tikzpicture}
#+end_src
I get the following
\resizebox{.9\linewidth}{!}{\input{foldleft.tikz}}
How can I change the parameter of the resizebox command? I tried adding
a line
#+attr_latex :width \linewidth
as I usually do for images, but it is not taken into account.
Thanks,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂ (2016-01, Mauna Loa Obs.): 402.52
signature.asc
Description: PGP signature
[O] Cannot export bash src: more details
Hello, regarding my previous message: I discovered that, by removing indentation, the export works fine. More specifically, the following snippet produces the error: %- snippet --% ** CGI - producing output - Example in shell script: #+BEGIN_SRC bash echo "content-type: text/html" echo echo "" echo "" echo "" echo "it is "`date`"" echo "" echo "" #+END_SRC %- snippet --% %- Error --% [...] org-babel-exp process emacs-lisp at line 16... org-babel-exp process html at line 114... org-babel-exp process html at line 164... org-babel-exp process bash at line 270... byte-code: Invalid search bound (wrong side of point) %- Error --% The following snippet *does not* produce the error %- snippet --% ** CGI - producing output - Example in shell script: #+BEGIN_SRC bash echo "content-type: text/html" echo echo "" echo "" echo "" echo "it is "`date`"" echo "" echo "" #+END_SRC %- snippet --% I cannot easily reproduce this behaviour outside of my complex file. I tried on a simplified version containing only the snippet, and there indentation makes no difference. Unfortunately, I do not have time now to continue my investigation (I have to prepare my slides for tomorrow), however I am available to provide more information if necessary. Org-mode version 8.3.4 (release_8.3.4-588-g924431 @ /home/lipari/elisp/org-mode/lisp/) Best regards, Giuseppe Lipari
Re: [O] Bug: :export results does not replace previous results designated block
Hi Nicolas,
On 02/22/2016 03:17 PM, Nicolas Goaziou wrote:
Hello,
Charles Millar writes:
The last time (last Wednesday or so) I executed the following code
** Some subheading
#+NAME: SCHEDAP
#+begin_src rec :data foo.rec :type Finance :fields
AssetDate,Description,Basis :results silent
(File = 'Estate' && AccountSchedule = 'A')
#+end_src
#+RESULTS: SCHEDAP
#+NAME: SCHEDA
#+begin_src emacs-lisp :var table=SCHEDAP :exports results
(setq table (cons 'hline table))
(setq table (cons '("Date" "Description" "Inventory Value") table))
(setq table (append table '(("|Total Schedule A"
(setq table (append table '(("\n#+TBLFM:
@>$>=vsum(@I$>..@>>$>);%.2f::"
table
#+end_src
#+ATTR_LATEX: :mode table :environment longtable :align
p{60pt}p{300pt}N{8}{2}
#+TBLNAME: SCHEDA
[...]
Should I change the code blocks or is this a bug? All of tables
generated by the same or similar code behave the same way - a table
after #+RESULTS: foobar is , but nothing for #+TBLNAME: foobar.
What happens if you replace TBLNAME with NAME?
Same results. I have avoided changing TBLNAME to NAME, though I am not
sure if I have any reason other than habit.
Best,
Charlie
Re: [O] Bug: :export results does not replace previous results designated block
Hello,
Charles Millar writes:
> On 02/22/2016 03:17 PM, Nicolas Goaziou wrote:
>> Hello,
>>
>> Charles Millar writes:
>>
>>> The last time (last Wednesday or so) I executed the following code
>>>
>>> ** Some subheading
>>> #+NAME: SCHEDAP
>>> #+begin_src rec :data foo.rec :type Finance :fields
>>> AssetDate,Description,Basis :results silent
>>>(File = 'Estate' && AccountSchedule = 'A')
>>> #+end_src
>>> #+RESULTS: SCHEDAP
>>> #+NAME: SCHEDA
>>> #+begin_src emacs-lisp :var table=SCHEDAP :exports results
>>> (setq table (cons 'hline table))
>>> (setq table (cons '("Date" "Description" "Inventory Value") table))
>>> (setq table (append table '(("|Total Schedule A"
>>> (setq table (append table '(("\n#+TBLFM:
>>> @>$>=vsum(@I$>..@>>$>);%.2f::"
>>> table
>>> #+end_src
>>> #+ATTR_LATEX: :mode table :environment longtable :align
>>> p{60pt}p{300pt}N{8}{2}
>>> #+TBLNAME: SCHEDA
>> [...]
>>
>>> Should I change the code blocks or is this a bug? All of tables
>>> generated by the same or similar code behave the same way - a table
>>> after #+RESULTS: foobar is , but nothing for #+TBLNAME: foobar.
>> What happens if you replace TBLNAME with NAME?
>>
>>
> Same results. I have avoided changing TBLNAME to NAME, though I am not
> sure if I have any reason other than habit.
The problem is that TBLNAME is deprecated and very confusing.
Actually, here, you seem to be using it as #+RESULTS: (which is
different from #+NAME). You should replace it with #+RESULTS, since you
want to insert the /results/ of "SCHEDA" code evaluation below.
Regards,
--
Nicolas Goaziou
[O] * [[shell:cat ~/tmp | grep "asdf :: "]] does not work.
Hi, the maintainer of the Debian org-mode package referred me to this list for my bug report. Best regards, Josef. On Sun, Feb 21, 2016 at 11:10:52AM +0100, Josef Atmin wrote: > Package: org-mode > Version: 8.3.3-3 > Severity: normal > > Dear Maintainer, > > when a shell command in an unnumbered list includes '::', it is not > recognized as a shell > command anymore. > > To reproduce the bug, paste the following two lines in file 'tmp' > > asdf :: asdf > asdf :: qwer > > and add the following shell commands to an org file > >* [[shell:cat ~/tmp | grep "asdf :"]] >* [[shell:cat ~/tmp | grep "asdf ::"]] >* [[shell:cat ~/tmp | grep "asdf :: "]] > > If you klick on them you will probably find that the first two work while the > last one > does not, presumably because it is interpreted as a description list entry. > Interestingly, if you use a numbered list > >1. [[shell:cat ~/tmp | grep "asdf :"]] >2. [[shell:cat ~/tmp | grep "asdf ::"]] >3. [[shell:cat ~/tmp | grep "asdf :: "]] > > then all three work. > > Thanks for this great piece of software, I use it all the time. > > Best wishes, > > Josef. > > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages org-mode depends on: > ii emacs24 24.5+1-6+b1 > ii emacsen-common 2.0.8 > > Versions of packages org-mode recommends: > ii texlive-generic-recommended 2015.20160215-1 > ii texlive-latex-recommended2015.20160215-1 > > Versions of packages org-mode suggests: > pn ditaa > ii texlive-fonts-recommended 2015.20160215-1 > ii texlive-latex-extra2015.20160117-1 > > -- no debconf information
Re: [O] scheduled task without headline?
hymie! writes: > Greetings. > > I've got my notes organized mostly like this: > * major task > - note > - note > - note > ** minor task >- note >- note > ** minor task >- note >- note > > Now I have a "note" that I need to attach a "schedule" to (something I > have to do tomorrow). However, when I try to do something like this: > > - TODO note > SCHEDULED <2016-02-23 Tue> > > the agenda shows me the nearest headline > Scheduled: minor task > > I'd really like to have my specific "note" listed in the agenda, but > what I need to do is so minor that I don't want it to have a "headline" > in my notes. Is this possible? AFAIK no. You can have a task with check boxes: - [ ]. Rasmus -- Vote for Dick Taid in an election near you!
Re: [O] Auto-delete dated DONE notifications?
Hi all On Sat, Feb 20, 2016 at 2:00 PM, Nicolas Goaziou wrote: > I think this would be a nice addition to Org. Yes, it has been the wish of several users including me earlier on this list. > We could add an option that can limit the number of state change > notes in an entry. My only "contribution" to this subject is to suggest to reuse the existing option org-log-into-drawer and ":LOG_INTO_DRAWER:" respectively and to extend its possible values. Michael
Re: [O] Bug: :export results does not replace previous results designated block
On 02/23/2016 09:44 AM, Nicolas Goaziou wrote:
Hello,
Charles Millar writes:
On 02/22/2016 03:17 PM, Nicolas Goaziou wrote:
Hello,
Charles Millar writes:
The last time (last Wednesday or so) I executed the following code
** Some subheading
#+NAME: SCHEDAP
#+begin_src rec :data foo.rec :type Finance :fields
AssetDate,Description,Basis :results silent
(File = 'Estate' && AccountSchedule = 'A')
#+end_src
#+RESULTS: SCHEDAP
#+NAME: SCHEDA
#+begin_src emacs-lisp :var table=SCHEDAP :exports results
(setq table (cons 'hline table))
(setq table (cons '("Date" "Description" "Inventory Value") table))
(setq table (append table '(("|Total Schedule A"
(setq table (append table '(("\n#+TBLFM:
@>$>=vsum(@I$>..@>>$>);%.2f::"
table
#+end_src
#+ATTR_LATEX: :mode table :environment longtable :align
p{60pt}p{300pt}N{8}{2}
#+TBLNAME: SCHEDA
[...]
Should I change the code blocks or is this a bug? All of tables
generated by the same or similar code behave the same way - a table
after #+RESULTS: foobar is , but nothing for #+TBLNAME: foobar.
What happens if you replace TBLNAME with NAME?
Same results. I have avoided changing TBLNAME to NAME, though I am not
sure if I have any reason other than habit.
The problem is that TBLNAME is deprecated and very confusing.
Actually, here, you seem to be using it as #+RESULTS: (which is
different from #+NAME). You should replace it with #+RESULTS, since you
want to insert the /results/ of "SCHEDA" code evaluation below.
Thanks, Nicolas.
I'll change all TBLNAME's to RESULTS; it seems to work. (There are files
that go back to 2010 or so.)
I was aware of the deprecation; it just that I was getting away with
using TBLNAME and hoped that I could continue to do so. Well, it caught
up with me in the past four or five days.
Charlie
Re: [O] scheduled task without headline?
On Mo, 2016-02-22 at 21:09, hymie! wrote: > I'd really like to have my specific "note" listed in the agenda, but > what I need to do is so minor that I don't want it to have a "headline" > in my notes. Is this possible? Have you already checked the so called inline tasks? C-h f org-inlinetask-insert-task Best regards -- Michael Strey http://www.strey.biz * https://twitter.com/michaelstrey
Re: [O] * [[shell:cat ~/tmp | grep "asdf :: "]] does not work.
* Nah, tried it, all 3 have same output: * [[shell:cat ~/tmp | grep "asdf :"]] * [[shell:cat ~/tmp | grep "asdf ::"]] * [[shell:cat ~/tmp | grep "asdf :: "]] => Executing cat ~/tmp | grep "asdf :" asdf :: asdf asdf :: qwer Executing cat ~/tmp | grep "asdf ::" asdf :: asdf asdf :: qwer Executing cat ~/tmp | grep "asdf :: " asdf :: asdf asdf :: qwer On Mon, Feb 22, 2016 at 3:59 AM, Josef Atmin wrote: > Hi, > > the maintainer of the Debian org-mode package referred me to this list for > my bug report. > > Best regards, Josef. > > On Sun, Feb 21, 2016 at 11:10:52AM +0100, Josef Atmin wrote: > > Package: org-mode > > Version: 8.3.3-3 > > Severity: normal > > > > Dear Maintainer, > > > > when a shell command in an unnumbered list includes '::', it is not > recognized as a shell > > command anymore. > > > > To reproduce the bug, paste the following two lines in file 'tmp' > > > > asdf :: asdf > > asdf :: qwer > > > > and add the following shell commands to an org file > > > >* [[shell:cat ~/tmp | grep "asdf :"]] > >* [[shell:cat ~/tmp | grep "asdf ::"]] > >* [[shell:cat ~/tmp | grep "asdf :: "]] > > > > If you klick on them you will probably find that the first two work > while the last one > > does not, presumably because it is interpreted as a description list > entry. > > Interestingly, if you use a numbered list > > > >1. [[shell:cat ~/tmp | grep "asdf :"]] > >2. [[shell:cat ~/tmp | grep "asdf ::"]] > >3. [[shell:cat ~/tmp | grep "asdf :: "]] > > > > then all three work. > > > > Thanks for this great piece of software, I use it all the time. > > > > Best wishes, > > > > Josef. > > > > > > -- System Information: > > Debian Release: stretch/sid > > APT prefers unstable > > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > Init: systemd (via /run/systemd/system) > > > > Versions of packages org-mode depends on: > > ii emacs24 24.5+1-6+b1 > > ii emacsen-common 2.0.8 > > > > Versions of packages org-mode recommends: > > ii texlive-generic-recommended 2015.20160215-1 > > ii texlive-latex-recommended2015.20160215-1 > > > > Versions of packages org-mode suggests: > > pn ditaa > > ii texlive-fonts-recommended 2015.20160215-1 > > ii texlive-latex-extra2015.20160117-1 > > > > -- no debconf information > >
Re: [O] * [[shell:cat ~/tmp | grep "asdf :: "]] does not work.
* Only way I can explain why the "3rd output is different from the 1st and 2nd": You unwittingly placed a character after the "::" on the 3rd row--and you look at it and you believe its a character. * Suggest you open it up in VI and do ":set list"--is there a "^I" character there? ** Better yet, open the file up and use whitespace-mode in Emacs. ** Also suggest you use the POSIX compliant form for regular expressions whenever possible--i.e. use [:blank:] when you mean " " and "[:space:]" when you mean whitespace--that way its harder to fool yourself, and others that read your code. On Tue, Feb 23, 2016 at 4:11 PM, briangpowell . wrote: > * Nah, tried it, all 3 have same output: > > * [[shell:cat ~/tmp | grep "asdf :"]] > * [[shell:cat ~/tmp | grep "asdf ::"]] > * [[shell:cat ~/tmp | grep "asdf :: "]] > > => > > Executing cat ~/tmp | grep "asdf :" > asdf :: asdf > asdf :: qwer > Executing cat ~/tmp | grep "asdf ::" > asdf :: asdf > asdf :: qwer > Executing cat ~/tmp | grep "asdf :: " > asdf :: asdf > asdf :: qwer > > > On Mon, Feb 22, 2016 at 3:59 AM, Josef Atmin wrote: > >> Hi, >> >> the maintainer of the Debian org-mode package referred me to this list >> for my bug report. >> >> Best regards, Josef. >> >> On Sun, Feb 21, 2016 at 11:10:52AM +0100, Josef Atmin wrote: >> > Package: org-mode >> > Version: 8.3.3-3 >> > Severity: normal >> > >> > Dear Maintainer, >> > >> > when a shell command in an unnumbered list includes '::', it is not >> recognized as a shell >> > command anymore. >> > >> > To reproduce the bug, paste the following two lines in file 'tmp' >> > >> > asdf :: asdf >> > asdf :: qwer >> > >> > and add the following shell commands to an org file >> > >> >* [[shell:cat ~/tmp | grep "asdf :"]] >> >* [[shell:cat ~/tmp | grep "asdf ::"]] >> >* [[shell:cat ~/tmp | grep "asdf :: "]] >> > >> > If you klick on them you will probably find that the first two work >> while the last one >> > does not, presumably because it is interpreted as a description list >> entry. >> > Interestingly, if you use a numbered list >> > >> >1. [[shell:cat ~/tmp | grep "asdf :"]] >> >2. [[shell:cat ~/tmp | grep "asdf ::"]] >> >3. [[shell:cat ~/tmp | grep "asdf :: "]] >> > >> > then all three work. >> > >> > Thanks for this great piece of software, I use it all the time. >> > >> > Best wishes, >> > >> > Josef. >> > >> > >> > -- System Information: >> > Debian Release: stretch/sid >> > APT prefers unstable >> > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') >> > Architecture: amd64 (x86_64) >> > Foreign Architectures: i386 >> > >> > Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) >> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) >> > Shell: /bin/sh linked to /bin/dash >> > Init: systemd (via /run/systemd/system) >> > >> > Versions of packages org-mode depends on: >> > ii emacs24 24.5+1-6+b1 >> > ii emacsen-common 2.0.8 >> > >> > Versions of packages org-mode recommends: >> > ii texlive-generic-recommended 2015.20160215-1 >> > ii texlive-latex-recommended2015.20160215-1 >> > >> > Versions of packages org-mode suggests: >> > pn ditaa >> > ii texlive-fonts-recommended 2015.20160215-1 >> > ii texlive-latex-extra2015.20160117-1 >> > >> > -- no debconf information >> >> >
Re: [O] * [[shell:cat ~/tmp | grep "asdf :: "]] does not work.
Dear briangpowell, there is definitely a space in the third line. Also, it does not simply produce no output, it says "No link found". Plus, when I change it to a numbered list starting with 1., 2., 3. it works. I have also run this with my .emacs file disabled, so it cannot be my option settings. Are you sure you use the same emacs and org-mode version as I do? I use emacs46.1 emacs24 24.5+1-6+b1 org-mode 8.3.3-3 What else could it be that makes our systems behave differently? Best regards, Josef. On Tue, Feb 23, 2016 at 04:31:23PM -0500, briangpowell . wrote: > * Only way I can explain why the "3rd output is different from the 1st and > 2nd": > > You unwittingly placed a character after the "::" on the 3rd row--and > you look at it and you believe its a character. > > * Suggest you open it up in VI and do ":set list"--is there a "^I" > character there? > > ** Better yet, open the file up and use whitespace-mode in Emacs. > > ** Also suggest you use the POSIX compliant form for regular expressions > whenever possible--i.e. use [:blank:] when you mean " " and "[:space:]" > when you mean whitespace--that way its harder to fool yourself, and others > that read your code. > > > > > > > On Tue, Feb 23, 2016 at 4:11 PM, briangpowell . > wrote: > > > * Nah, tried it, all 3 have same output: > > > > * [[shell:cat ~/tmp | grep "asdf :"]] > > * [[shell:cat ~/tmp | grep "asdf ::"]] > > * [[shell:cat ~/tmp | grep "asdf :: "]] > > > > => > > > > Executing cat ~/tmp | grep "asdf :" > > asdf :: asdf > > asdf :: qwer > > Executing cat ~/tmp | grep "asdf ::" > > asdf :: asdf > > asdf :: qwer > > Executing cat ~/tmp | grep "asdf :: " > > asdf :: asdf > > asdf :: qwer > > > > > > On Mon, Feb 22, 2016 at 3:59 AM, Josef Atmin wrote: > > > >> Hi, > >> > >> the maintainer of the Debian org-mode package referred me to this list > >> for my bug report. > >> > >> Best regards, Josef. > >> > >> On Sun, Feb 21, 2016 at 11:10:52AM +0100, Josef Atmin wrote: > >> > Package: org-mode > >> > Version: 8.3.3-3 > >> > Severity: normal > >> > > >> > Dear Maintainer, > >> > > >> > when a shell command in an unnumbered list includes '::', it is not > >> recognized as a shell > >> > command anymore. > >> > > >> > To reproduce the bug, paste the following two lines in file 'tmp' > >> > > >> > asdf :: asdf > >> > asdf :: qwer > >> > > >> > and add the following shell commands to an org file > >> > > >> >* [[shell:cat ~/tmp | grep "asdf :"]] > >> >* [[shell:cat ~/tmp | grep "asdf ::"]] > >> >* [[shell:cat ~/tmp | grep "asdf :: "]] > >> > > >> > If you klick on them you will probably find that the first two work > >> while the last one > >> > does not, presumably because it is interpreted as a description list > >> entry. > >> > Interestingly, if you use a numbered list > >> > > >> >1. [[shell:cat ~/tmp | grep "asdf :"]] > >> >2. [[shell:cat ~/tmp | grep "asdf ::"]] > >> >3. [[shell:cat ~/tmp | grep "asdf :: "]] > >> > > >> > then all three work. > >> > > >> > Thanks for this great piece of software, I use it all the time. > >> > > >> > Best wishes, > >> > > >> > Josef. > >> > > >> > > >> > -- System Information: > >> > Debian Release: stretch/sid > >> > APT prefers unstable > >> > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') > >> > Architecture: amd64 (x86_64) > >> > Foreign Architectures: i386 > >> > > >> > Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) > >> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > >> > Shell: /bin/sh linked to /bin/dash > >> > Init: systemd (via /run/systemd/system) > >> > > >> > Versions of packages org-mode depends on: > >> > ii emacs24 24.5+1-6+b1 > >> > ii emacsen-common 2.0.8 > >> > > >> > Versions of packages org-mode recommends: > >> > ii texlive-generic-recommended 2015.20160215-1 > >> > ii texlive-latex-recommended2015.20160215-1 > >> > > >> > Versions of packages org-mode suggests: > >> > pn ditaa > >> > ii texlive-fonts-recommended 2015.20160215-1 > >> > ii texlive-latex-extra2015.20160117-1 > >> > > >> > -- no debconf information > >> > >> > >
[O] "No link found" for after <2016-02-21 Sun>
Hi, the maintainer of the Debian org-mode package referred me to this list for my bug report. Best regards, Josef. On Sun, Feb 21, 2016 at 11:29:03AM +0100, Josef Atmin wrote: > Package: org-mode > Version: 8.3.3-3 > Severity: normal > > Dear Maintainer, > > when the curser is at the end of the line directly after <2016-02-21 Sun>, > i.e. there > comes a newline right after the '>', then typing results in the > message "No link > found". I guess this is a bug. > > When I add a space between <2016-02-21 Sun> and the newline, then typing > when > the curser sits on the space brings up agenda mode for that date. I guess > this is the > intended behavior. > > I actually find both behaviors anoying and would much rather prefer if simply > a newline > is inserted when I type AFTER <2016-02-21 Sun>. Typing return on the > <2016-02-21 Sun> should, of course, bring up agenda mode for that date. The > same applies > to regular shell commands of the form [[shell...]] or [[file...]]. The > problem is, that > I quite often run into the situation that I want have a line break right > after such a > date and command, and each time I accidentally rund the command or date. So > this is my > wishlist part. > > I think this is a new feature you have added in one of the recent versions. > So I would > strongly vote for reverting that. > > I use the following options, and I would like to keep them: > > ;; configure link behavior > ; don't ask for confirmation when klicking on a shell link > (setq org-confirm-shell-link-function nil) > ; follow a link when pressing return on it > (setq org-return-follows-link t) > > Best wishes, > > Josef. > > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages org-mode depends on: > ii emacs24 24.5+1-6+b1 > ii emacsen-common 2.0.8 > > Versions of packages org-mode recommends: > ii texlive-generic-recommended 2015.20160215-1 > ii texlive-latex-recommended2015.20160215-1 > > Versions of packages org-mode suggests: > pn ditaa > ii texlive-fonts-recommended 2015.20160215-1 > ii texlive-latex-extra2015.20160117-1 > > -- no debconf information
Re: [O] "No link found" for after <2016-02-21 Sun>
Hello, Josef Atmin writes: >> when the curser is at the end of the line directly after <2016-02-21 Sun>, >> i.e. there >> comes a newline right after the '>', then typing results in the >> message "No link >> found". I guess this is a bug. This is fixed in development version already (commit a87c34cb8d58e7019c8d081c02bbac9e93cef8ab). Regards, -- Nicolas Goaziou
[O] (message "Greedy org-protocol handler. Killing client.")
org-protocol works less than half the time now. i try it with the org-capture firefox extension on iceweasel. i also try it with a manual bookmark created by some instruction somewhere. today every click puts this in my messages buffer: "Greedy org-protocol handler. Killing client." could somebody please explain what this means? i do not understand the code. org maint. thanks. -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. And ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] "No link found" for after <2016-02-21 Sun>
Dear Nicolas! On Tue, Feb 23, 2016 at 11:34:21PM +0100, Nicolas Goaziou wrote: > Hello, > > Josef Atmin writes: > > >> when the curser is at the end of the line directly after <2016-02-21 Sun>, > >> i.e. there > >> comes a newline right after the '>', then typing results in the > >> message "No link > >> found". I guess this is a bug. > > This is fixed in development version already (commit > a87c34cb8d58e7019c8d081c02bbac9e93cef8ab). Thanks for letting me know. I guess it will make it to the unstable release soon. So there remains my wishlist item, namely that typing after a link results in a newline rather than activation of the link. I would find it much better if only a on the link would activate it, because I am often in the situation where I am at the end of a line and I want to insert a newline, but because there is a link at the end of the line right before the curser (not at the cursor), the link is activated, which is mostly harmless but anoying. To avoid that, I have to either first tiype a and then a or first Ctrl-o and then . But it is hard for me to always be aware of the link and change my automatism of simply typing . I believe that this behavior has actually changed in one of the recent versions. Can anybody point me to the discussion in which this change (to activating the link upon if the curser is behind the link) was decided, so that I can understand the arguments for this behavior that I personally don't like. Best wishes, Josef.
Re: [O] how to change the resizebox for a generated tikz diagram?
Hello,
On 2016-02-23 11:37, Alan Schmitt writes:
> When exporting this source block to beamer
>
> #+header: :file (by-backend (beamer "foldleft.tikz") (t "foldleft.png"))
> #+header: :imagemagick yes :iminoptions -density 600 :imoutoptions -geometry
> 800
> #+header: :results file raw
> #+header: :headers '("\\usepackage{tikz}")
> #+begin_src latex
> \usetikzlibrary{matrix,arrows}
> \begin{tikzpicture}[scale=2, every node/.style={transform shape}]
> \matrix (m) [matrix of nodes, row sep=2em, column sep=3em]
> { & $[x_1;$ & $x_2;$ & $\ldots;$ & $x_n]$ & \\
> $acc$ & \node (f1) [circle, draw] {$f$}; & \node (f2) [circle,draw] {$f$};
> & & \node (fn) [circle,draw] {$f$}; & \texttt{fold\_left } $f$ \; $acc$ \;
> $[x_1; x_2; \ldots; x_n]$\\
> };
> \draw (m-2-1) edge[->,thick] (f1);
> \draw (f1) edge[->,thick] (f2);
> \draw (f2) edge[->,thick,dotted] (fn);
> \draw (fn) edge[->,thick] (m-2-6);
> \draw (m-1-2) edge[->,thick] (f1);
> \draw (m-1-3) edge[->,thick] (f2);
> \draw (m-1-5) edge[->,thick] (fn);
> \end{tikzpicture}
> #+end_src
>
> I get the following
>
> \resizebox{.9\linewidth}{!}{\input{foldleft.tikz}}
>
> How can I change the parameter of the resizebox command? I tried adding
> a line
> #+attr_latex :width \linewidth
> as I usually do for images, but it is not taken into account.
I've found a workaround: I add
#+name: foldleft
before the block, and then I can put the attr_latex before an explicit
result block:
#+attr_latex: :width \linewidth
#+results: foldleft
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂ (2016-01, Mauna Loa Obs.): 402.52
signature.asc
Description: PGP signature
