[O] [BUG] org-table-beginning/end-of-field
Hi, The argument of `org-table-beginning-of-field' and `org-table-end-of-field' is in fact not optional. -- Florian Beck >From d1d12380a1c260bef7a2137831434614f7d9ec1f Mon Sep 17 00:00:00 2001 From: Florian Beck Date: Mon, 8 Sep 2014 07:34:56 +0200 Subject: [PATCH] Remove &optional argument spec * lisp/org-table.el (org-table-beginning-of-field): fix argument (org-table-end-of-field): fix argument --- lisp/org-table.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/org-table.el b/lisp/org-table.el index 547f933..a17e95a 100644 --- a/lisp/org-table.el +++ b/lisp/org-table.el @@ -1061,7 +1061,7 @@ Before doing so, re-align the table if necessary." (if (looking-at "| ?") (goto-char (match-end 0 -(defun org-table-beginning-of-field (&optional n) +(defun org-table-beginning-of-field (n) "Move to the end of the current table field. If already at or after the end, move to the end of the next table field. With numeric argument N, move N-1 fields forward first." @@ -1076,7 +1076,7 @@ With numeric argument N, move N-1 fields forward first." (and (looking-at " ") (forward-char 1))) (if (>= (point) pos) (org-table-beginning-of-field 2 -(defun org-table-end-of-field (&optional n) +(defun org-table-end-of-field (n) "Move to the beginning of the current table field. If already at or before the beginning, move to the beginning of the previous field. -- 1.9.1
Re: [O] Does org-protocol work with Chrome on windows?
> It definitely works with Chrome/Windows. It does and I would have known if I didn't assume that the URL bar works the same way in Firefox and Chrome and just tested the javascript's links in the "Verify the installation" section. Merci Fabrice, sorry for the noise. Bruno 2014-09-08 0:33 GMT-04:00 Fabrice Popineau : > It definitely works with Chrome/Windows. > > Fabrice > > 2014-09-07 23:57 GMT+02:00 Bruno Bigras : >> >> Hi, >> >> I registred org-protocol[1] but org-protocol://capture://test doesn't >> work (it does a google search). It seems to work with Firefox. >> >> Is it supposed to work with Chrome on Windows? >> >> Thanks, >> >> Bruno >> >> [1] : http://orgmode.org/worg/org-contrib/org-protocol.html#sec-3-3 >> > > > > -- > Fabrice Popineau > - > SUPELEC > Département Informatique > 3, rue Joliot Curie > 91192 Gif/Yvette Cedex > Tel direct : +33 (0) 169851950 > Standard : +33 (0) 169851212 > -- >
Re: [O] Does org-protocol work with Chrome on windows?
It definitely works with Chrome/Windows. Fabrice 2014-09-07 23:57 GMT+02:00 Bruno Bigras : > Hi, > > I registred org-protocol[1] but org-protocol://capture://test doesn't > work (it does a google search). It seems to work with Firefox. > > Is it supposed to work with Chrome on Windows? > > Thanks, > > Bruno > > [1] : http://orgmode.org/worg/org-contrib/org-protocol.html#sec-3-3 > > -- Fabrice Popineau - SUPELEC Département Informatique 3, rue Joliot Curie 91192 Gif/Yvette Cedex Tel direct : +33 (0) 169851950 Standard : +33 (0) 169851212 --
[O] Does org-protocol work with Chrome on windows?
Hi, I registred org-protocol[1] but org-protocol://capture://test doesn't work (it does a google search). It seems to work with Firefox. Is it supposed to work with Chrome on Windows? Thanks, Bruno [1] : http://orgmode.org/worg/org-contrib/org-protocol.html#sec-3-3
Re: [O] org-edit-special doesn't work within #+BEGIN_LaTeX blocks anymore
Hello, Eric S Fraga writes: > I ran into this change today. I like being able to edit latex in its > own mode without having to resort to babel. Actually, this is a consequence of a known bug. See my last reply in thread at http://permalink.gmane.org/gmane.emacs.orgmode/90336 Regards, -- Nicolas Goaziou
Re: [O] org-edit-special doesn't work within #+BEGIN_LaTeX blocks anymore
On Sunday, 7 Sep 2014 at 10:32, Julien Cubizolles wrote: > It used to work, but the latest from git gives > > user-error: No special environment to edit here > > It was very convenient to use auctex from within an org file using a lot > of LaTeX formulas. Is there a reason to change this behaviour ? +1 I ran into this change today. I like being able to edit latex in its own mode without having to resort to babel. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.1, Org release_8.3beta-310-g38d0eb signature.asc Description: PGP signature
[O] Clock start time is gone
Hello, I'm moving point over a habit in the agenda, clocking on with I, switching buffer a few times, then switching back and hitting O. Occasionally, I get a "Clock start time is gone" message. I just got one now. If I go to the node, I see this: :LOGBOOK: CLOCK: [2014-09-07 Sun 19:41] - State "DONE" from "TODO" [2014-09-01 Mon 22:46] CLOCK: [2014-09-01 Mon 22:01]--[2014-09-01 Mon 22:46] => 0:45 ... So this doesn't make any sense. The clock start time is right there! Any idea? Thanks, -- Noah Slater https://twitter.com/nslater
Re: [O] export to man page problem
On Sun, 07 Sep 2014 10:14:59 +0200
Nicolas Goaziou wrote:
> Manfred Lotz writes:
>
> > Take this
> >
> > <--snip>
> > #+TITLE: mycmd
> > * NAME
> > mycmd - does very important things
> > * SYNOPSIS
> > mycmd.pl -u bla [-R] [-A] [-n] [-a]
> > * DESCRIPTION
> > mycmd could be configured by setting environment variable MYCMD_OPT
> > <--snap>
> >
> > The man page looks like this:
> >
> > mycmd(1) General Commands
> > Manual mycmd(1)
> >
> >
> >
> > NAME
> >mycmd - does very important things
> >
> > SYNOPSIS
> >mycmd.pl -u bla [-R] [-A] [-n] [-a]
> >
> > DESCRIPTION
> >mycmd could be configured by setting environment variable
> > MYCMDOPT
> >
> >
> >
> > As you can see the _ (underscore) in MYCMD_OPT vanished.
>
> In this case, "_OPT" is a subscript, which is translated into
> "MYCMD\d\s-2OPT\s+2\u". For some reason, groff doesn't recognize this
> markup.
>
> Anyway, you probably don't want a subscript here. Locally, you can use
> a macro instead:
>
> MYCMD\under{}OPT
>
> or simply disable subscript (and superscript) for the whole document:
>
> #+OPTIONS: ^:nil
>
>
In this case I prefer the OPTINS version. However, it is good to know I
just could use \under.
Thanks a lot for your help.
--
Manfred
[O] Bug: aborting capture to new file leaves 1-byte file behind [8.2.7c]
I'm using a capture template to create a new file (via read-file-name) with some pre-filled #+STARTUP options. I'm using immediate-finish, but while I was setting it up I noticed that captures to a new file will leave behind a 1-byte file (containing a newline) if aborted with org-capture-kill. To replicate, just add a new capture template pointing to a non-existent file, start capturing to it, then abort. === Emacs : GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of 2014-06-06 on barber, modified by Debian Package: Org-mode version 8.2.7c (8.2.7c-dist @ /usr/share/emacs24/site-lisp/org-mode/) -- Ben Winslow
[O] org-edit-special doesn't work within #+BEGIN_LaTeX blocks anymore
It used to work, but the latest from git gives --8<---cut here---start->8--- user-error: No special environment to edit here --8<---cut here---end--->8--- It was very convenient to use auctex from within an org file using a lot of LaTeX formulas. Is there a reason to change this behaviour ? Julien.
Re: [O] export to man page problem
Manfred Lotz writes:
> Take this
>
> <--snip>
> #+TITLE: mycmd
> * NAME
> mycmd - does very important things
> * SYNOPSIS
> mycmd.pl -u bla [-R] [-A] [-n] [-a]
> * DESCRIPTION
> mycmd could be configured by setting environment variable MYCMD_OPT
> <--snap>
>
> The man page looks like this:
>
> mycmd(1) General Commands
> Manual mycmd(1)
>
>
>
> NAME
>mycmd - does very important things
>
> SYNOPSIS
>mycmd.pl -u bla [-R] [-A] [-n] [-a]
>
> DESCRIPTION
>mycmd could be configured by setting environment variable
> MYCMDOPT
>
>
>
> As you can see the _ (underscore) in MYCMD_OPT vanished.
In this case, "_OPT" is a subscript, which is translated into
"MYCMD\d\s-2OPT\s+2\u". For some reason, groff doesn't recognize this
markup.
Anyway, you probably don't want a subscript here. Locally, you can use
a macro instead:
MYCMD\under{}OPT
or simply disable subscript (and superscript) for the whole document:
#+OPTIONS: ^:nil
Regards,
--
Nicolas Goaziou
Re: [O] export to man page problem
Hi Nicolas, Thanks for answering. On Sun, 07 Sep 2014 09:12:21 +0200 Nicolas Goaziou wrote: > Hello, > > Manfred Lotz writes: > > > When exporting to a man page an underscore will be translated to > > nothing. > > > > Any idea what I could do? > > Because I know close to nothing about Groff, could you give an example > illustrating > > 1. what you wrote, > 2. what you expected to have in the ".man" file, > 3. what you actually got. > > Take this <--snip> #+TITLE: mycmd * NAME mycmd - does very important things * SYNOPSIS mycmd.pl -u bla [-R] [-A] [-n] [-a] * DESCRIPTION mycmd could be configured by setting environment variable MYCMD_OPT <--snap> The man page looks like this: mycmd(1) General Commands Manual mycmd(1) NAME mycmd - does very important things SYNOPSIS mycmd.pl -u bla [-R] [-A] [-n] [-a] DESCRIPTION mycmd could be configured by setting environment variable MYCMDOPT As you can see the _ (underscore) in MYCMD_OPT vanished. -- Manfred
Re: [O] export to man page problem
Hello, Manfred Lotz writes: > When exporting to a man page an underscore will be translated to > nothing. > > Any idea what I could do? Because I know close to nothing about Groff, could you give an example illustrating 1. what you wrote, 2. what you expected to have in the ".man" file, 3. what you actually got. Regards, -- Nicolas Goaziou
