Joshua Meyers writes:
> In this page (https://orgmode.org/worg/org-gtd-etc.html) the link to
> the "very instructive post by Pete Phillips" now directs to the
> defunct gmane.org. I think I tracked down the post it is supposed
> to link to, so I don't want others to have to do this work again:
>
Hello,
Qqwy/Wiebe-Marten writes:
> I think the link should be changed to one of:
>
> - https://staff.fnwi.uva.nl/c.dominik/Tools/cdlatex/ , which seems to be
> the location that the original link was moved to.
>
> - https://github.com/cdominik/cdlatex , which is a repository containing
> the lat
2018-01-30 21:59 GMT+01:00 Nicolas Goaziou :
> Hello,
>
> Fabrice Popineau writes:
>
> > You should have a look at commit 38be85124551083d269.
> > It prevents evaluation of the by-backend form in parameters.
>
> It doesn't.
>
> My mistake: it optionaly prevents :-)
> It prevents evaluation con
Hello,
Fabrice Popineau writes:
> You should have a look at commit 38be85124551083d269.
> It prevents evaluation of the by-backend form in parameters.
It doesn't.
It prevents evaluation conditionally, i.e., when an optional argument is
non-nil. The same argument prevents expanding Noweb refer
> On Jan 28, 2018, at 11:49 PM, Fabrice Popineau
> wrote:
>
> You should have a look at commit 38be85124551083d269.
> It prevents evaluation of the by-backend form in parameters.
>
You are right.
I do not see a clean way to do what `by-backend' would have done prior to that
commit.
Maybe
2018-01-29 2:34 GMT+01:00 Berry, Charles :
> > On Jan 28, 2018, at 3:24 PM, Nicolas Goaziou
> wrote:
> >
> > Would you have an ECM? I don't know what is "the by-backend trick".
>
> Not a bug AFAICS.
>
> `by-backend' is a macro mentioned here:
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2
> On Jan 28, 2018, at 3:24 PM, Nicolas Goaziou wrote:
>
> Would you have an ECM? I don't know what is "the by-backend trick".
Not a bug AFAICS.
`by-backend' is a macro mentioned here:
https://lists.gnu.org/archive/html/emacs-orgmode/2013-07/msg00500.html
I guess it needs to use `org-export-
2018-01-29 0:24 GMT+01:00 Nicolas Goaziou :
> Hello,
>
> Fabrice Popineau writes:
>
> > Well, I think there is a problem with the current master
> > since commit 38be85124551083d269.
> >
> > The problem is that the by-backend trick which were tolerated before
> > does not work anymore.
> >
> > Te
Hello,
Fabrice Popineau writes:
> Well, I think there is a problem with the current master
> since commit 38be85124551083d269.
>
> The problem is that the by-backend trick which were tolerated before
> does not work anymore.
>
> Tested between Org 9.1.6 as in current emacs-26.0.91 release versus
Nicolas Goaziou twisted the bytes to say:
Nicolas> Hello,
Nicolas> dmg writes:
>> org-link-escape only replaces space, [, ], and %
>>
>> but search in google/gmail is replacing + also.
>>
>> The simplest solution is to add 43 to org-link-escape-chars:
>>
>> org-link-escape-chars is
Hello,
dmg writes:
> org-link-escape only replaces space, [, ], and %
>
> but search in google/gmail is replacing + also.
>
> The simplest solution is to add 43 to org-link-escape-chars:
>
>org-link-escape-chars is a variable defined in ‘org.el’.
>Its value is (32 91 93 37)
>
> This va
Hello,
Anders Papitto writes:
> I have org version 9.0.3 (and I've been noticing this the whole time I've
> used org - only just now reporting it), and this is 100% consistent for me.
>
> I often have two client frames open, connected to the same emacs daemon.
> One frame will be displaying the
Hello,
"Charles C. Berry" writes:
> On Wed, 1 Mar 2017, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> D M German writes:
>>
>>> So the original issue (* not being escaped) will nonetheless appear when
>>> the threshold is passed:
>>>
>>
>> Fixed. Thank you.
>>
>
> Hmmm. Now I get
>
> :FAILED te
On Wed, 1 Mar 2017, Nicolas Goaziou wrote:
Hello,
D M German writes:
So the original issue (* not being escaped) will nonetheless appear when
the threshold is passed:
Fixed. Thank you.
Hmmm. Now I get
:FAILED test-ob/org-babel-insert-result
for make test2, which appears to be fr
Hello,
D M German writes:
> So the original issue (* not being escaped) will nonetheless appear when
> the threshold is passed:
>
> Here is an example (I run it with emacs -nw -q, using emacs25) org
> version 8.2.10 (this works also in my configuration under 9.0.2)
>
> #+BEGIN_SRC emacs-lisp :re
Hi Charles, everybody,
>> I am running a babel script that generates, as one of its line * in the
>> front:
>>
>> #+BEGIN_SRC sh
>> echo "* Hello"
>> #+END_SRC
>>
>> #+RESULTS:
>> #+begin_example
>> * Hello
>> #+end_example
>>
>> In that case, should babel be the one escaping t
"Charles C. Berry" writes:
> On Mon, 27 Feb 2017, dmg wrote:
>
>> On Sun, Feb 26, 2017 at 11:40 PM, Nicolas Goaziou
>> wrote:
>>
>>>
>>> A star at the beginning of a line is always a headline.
>
> [...]
>
>>
>> Thank you. I guess the issue is then with org-babel.
>>
>> I am running a babel scri
On Mon, 27 Feb 2017, dmg wrote:
On Sun, Feb 26, 2017 at 11:40 PM, Nicolas Goaziou
wrote:
A star at the beginning of a line is always a headline.
[...]
Thank you. I guess the issue is then with org-babel.
I am running a babel script that generates, as one of its line * in the
front:
On Sun, Feb 26, 2017 at 11:40 PM, Nicolas Goaziou
wrote:
>
> A star at the beginning of a line is always a headline. It has
> precedence over the block around it. You need to escape the star
> character:
>
> #+begin_example
> ,* hello world
> #+end_example
>
> Regards,
Thank you. I guess
Hello,
dmg writes:
> The following example:
>
>
> * Example
>
> #+begin_example
> hello world
> #+end_example
>
> #+begin_example
> * hello world
> #+end_example
>
> exports an HTML file where the second "hello word" is interpreted as a
> header, ignoring that it is within begin_example. See bel
Nicolas Goaziou twisted the bytes to say:
>>
>> I am running version 9.0.3 of org.
>>
>> I believe this patch will solve the issue. It simply adds a space before
>> the class attribute.
Nicolas> It works but I eventually applied a slightly different patch. Thank
you
Nicolas> for both
Hello,
dmg writes:
> I have the following org-snippet:
>
> ---
> This is an example
>
> #+BEGIN_SRC sml -r -l "(*(ref:%s)*)" -n
> val x = 1
> fun f y = x + y (*(ref:f)*)
> val x = 2
> val y = 3
> val z = f(x+y) (*(ref:callf)*)
> #+END_S
Hello,
Dan writes:
> Here is how I reproduce the bug:
>
> In org-mode (latest version) write \alpha. Then, put the cursor
> somewhere in the word. Press C-c C-x \ in order to display nice utf
> letters (greek, superscript etc). Then move right with the keyboard.
> Emacs crashes every time.
I c
On Thursday, 18 Feb 2016 at 15:24, ilya shlyakhter wrote:
> When loading any org file, I'm getting "File mode specification error:
> (error "before first heading")" . This happens starting with
> release_8.3.3 ; with release_8.3.2 , no error. Emacs version is
> GNU Emacs 24.3.1 (x86_64-unknown-li
On Tue, Aug 25, 2015 at 7:22 PM, Josiah Schwab wrote:
> This is the first item in the 8.3 series changelog. There is a provided
> script to repair things.
Now I see that this new requirement is documented in Info manual
subsection 7.1 Property syntax. I had only checked subsection 2.8
Drawers.
Hello Jorge,
> In Org mode's info, I could not find any requirement that the property
> drawer must be the first thing in the entry.
This is the first item in the 8.3 series changelog. There is a provided
script to repair things.
http://orgmode.org/Changes.html
Hope that helps,
Josiah
Nicolas Goaziou writes:
> Hello,
>
> Sharon Kimble writes:
>
>> Yes, its still occurring even after closing and restarting emacs. In
>> fact I've just done this to check for certain, and this time it threw up
>> a debugger page, which says -
>>
>> Debugger entered--Lisp error: (wrong-number-of-a
Hello,
Sharon Kimble writes:
> Yes, its still occurring even after closing and restarting emacs. In
> fact I've just done this to check for certain, and this time it threw up
> a debugger page, which says -
>
> Debugger entered--Lisp error: (wrong-number-of-arguments #[(pos)
> "r\302!\203\303
Sharon Kimble wrote:
> Kyle Meyer writes:
[...]
>> Just restarting emacs will still use the compiled files. Did you try
>> 'C-u M-x org-reload' (the C-u prefix loads the *.el files instead of
>> *.elc)?
>>
> I've just updated org+contrib to todays release, then done "reload org
> after update" f
Kyle Meyer writes:
> Sharon Kimble wrote:
> [...]
>>> Do you still get the error after running 'C-u M-x org-reload'?
>>>
>> Yes, its still occurring even after closing and restarting emacs.
>
> Just restarting emacs will still use the compiled files. Did you try
> 'C-u M-x org-reload' (the C-u
Kyle Meyer writes:
> Just restarting emacs will still use the compiled files. Did you try
> 'C-u M-x org-reload' (the C-u prefix loads the *.el files instead of
> *.elc)?
The org-reload uncompiled command is in the Org menu in Emacs under
Refresh/Reload and bound to "C-u C-c C-x !".
Regards,
Ac
Sharon Kimble writes:
> Kyle Meyer writes:
>
>> Do you still get the error after running 'C-u M-x org-reload'?
>>
> Yes, its still occurring even after closing and restarting emacs. In
> fact I've just done this to check for certain, and this time it threw up
> a debugger page, which says -
>
T
Sharon Kimble wrote:
[...]
>> Do you still get the error after running 'C-u M-x org-reload'?
>>
> Yes, its still occurring even after closing and restarting emacs.
Just restarting emacs will still use the compiled files. Did you try
'C-u M-x org-reload' (the C-u prefix loads the *.el files inste
Kyle Meyer writes:
> Hello,
>
> Sharon Kimble wrote:
>> I'm finding that when I clock out now I get the following error report
>
> I cannot reproduce this with 'emacs -Q' and the following test.
>
> Clocking in (C-c C-x C-i) and then out (C-c C-x C-o) on the following
> heading
>
> * h
>
> r
Hello,
Sharon Kimble wrote:
> I'm finding that when I clock out now I get the following error report
I cannot reproduce this with 'emacs -Q' and the following test.
Clocking in (C-c C-x C-i) and then out (C-c C-x C-o) on the following
heading
* h
results in
* h
:LOGBOOK:
On 15 May 2014 11:15, Bastien wrote:
> Hi Dave,
>
> Dave Pawson writes:
>
>> Section 4.2 Internal links
>> intimates (not clearly IMHO) that the target for a link in same file
>> is marked as <> yet a bad link offers to create one as
>> * #target
>> It is either wrong or unclear?
>> re
Hi Dave,
Dave Pawson writes:
> Section 4.2 Internal links
> intimates (not clearly IMHO) that the target for a link in same file
> is marked as <> yet a bad link offers to create one as
> * #target
> It is either wrong or unclear?
> regards DaveP dave.paw...@gmail.com
The manual says
Jason Lewis writes:
> 1. make a narrow frame, make sure only 1 window is open.
> 2. create an org buffer and enable org-beamer-mode
> 3. on a heading, press C-c C-b
> - the popup window is nicely formatted
>
> screenshot: http://take.ms/E389Mv
>
> 4. make the frame very wide, make sure only 1 w
Hi,
Nicolas Goaziou writes:
> Samuel Loury writes:
>
>> Use the following org sample:
>>
>> ---Beginning
>> * test1
>> #+BEGIN_EXAMPLE
>> * stuff
>> #+END_EXAMPLE
>> * test2
>> ---End
>
> Headlines have precedence over blocks. Therefore "* stuff" is really
> a headline in your ex
Hello,
Samuel Loury writes:
> I realized recently the following behavior, running on org version 8.0.3
> got from commit d7e884d86c8560477ca1e69fb8423db6770981ac (git sha).
>
> Use the following org sample:
>
> ---Beginning
> * test1
> #+BEGIN_EXAMPLE
> * stuff
> #+END_EXAMPLE
> * test2
Apologies, this seems to have been fixed in the latest development sources
for python-mode.el.
Please disregard.
Thanks,
Greg
On Tue, Jan 29, 2013 at 3:12 PM, Greg Novak wrote:
> If I load a python source file using python-mode.el, and then subsequently
> look at a .org file using org-mode.e
Hi Christopher,
Christopher Schmidt writes:
> Russell Branca writes:
>> While playing with org agenda mode and habits, I ran into the error:
>>
>> symbol's function definition is void "org-is-habit-p"
>>
>> The underlying problem was that org-habit did not get loaded. After
>> manually requirin
Russell Branca writes:
> While playing with org agenda mode and habits, I ran into the error:
>
> symbol's function definition is void "org-is-habit-p"
>
> The underlying problem was that org-habit did not get loaded. After
> manually requiring org-habit everything works as expected.
>
> If this i
Hannes Schulz writes:
> it seems to have forgotten that it should load init.el automatically.
> Any hint how I can fix this and avoid it next time?
Nope, sorry... maybe you deleted some part of your initial config
inadvertantly?
--
Bastien
Hi Bastien,
> On 31.08.2012, at 08:05, Bastien wrote:
> > This should be fixed now. Thanks to you and Jacob for
> > reporting this!
>
> Seems to work for me.
works for me too, thanks for fixing this so quickly!
A quick question: After playing with minimal configs, I now need to start emacs
wi
Hi Bastien,
On 31.08.2012, at 08:05, Bastien wrote:
> This should be fixed now. Thanks to you and Jacob for
> reporting this!
Seems to work for me.
Thanks!
Riko
Hi Hannes,
Hannes Schulz writes:
> when I put my agenda in column mode, I would like to change
> efforts and the like.
>
> When I do some action it instantly drops out of column mode.
This should be fixed now. Thanks to you and Jacob for
reporting this!
--
Bastien
Hi Hannes,
On 31.08.2012, at 03:52, Jacob Riko wrote:
> I was about to report the same behavior on a Mac:
Sorry for the noise, I actually do see the same behavior.
It is just that entering column-view in the file works fine, only a column view
on the agenda (C-c C-x C-c) throws the error.
Below
Hi Hannes,
I was about to report the same behavior on a Mac:
On 30.08.2012, at 13:47, Hannes Schulz wrote:
> when I put my agenda in column mode, I would like to change
> efforts and the like.
> When I do some action it instantly drops out of column mode.
>
> I'm using org-mode from git 7.9 (
James Atwood wrote:
> If an org file on the agenda list contains a header that is blank but
> for a date/timestamp, the weekly agenda command will fail. The resulting
> agenda buffer will be of type nil and contain only date headers.
>
This is probably the same bug that Ilya Shlyakhter report
Ilya Shlyakhter wrote:
> In the head revision, if the org file has headlines that start with a
> timestamp, the command to create a timeline of the file (C-a L)
> crashes.
>
>
> * things
> *** <2011-10-06 Thu 22:24>
>
> some text
>
>
> mapcar: Args out of range: #(" " 0 2 (org-category
Hello,
Markus Grebenstein writes:
> If of any interest I can try to reproduce this in a less than 9500
> word ducument.
Yes, I would appreciate an ECM (minimal complete example) along with the
version of Org you're using.
Thank you.
Regards,
--
Nicolas Goaziou
Hi Torsten,
Torsten Wagner writes:
> The error message on export was correct to say
> org-export-latex-set-initial-vars: No definition for class
> `koma_article ' in `org-export-latex-classes' (again notice the space)
Should be fixed now, thanks!
--
Bastien
Hello,
"Colin Fraizer" writes:
> Please pardon my ignorance, but I don't know how to generate a patch for
> distribution.
You have all instructions you want at:
http://orgmode.org/worg/org-contribute.html
If you don't want/can't follow them, please tell me. I will push your
patc
On Wed, Oct 12, 2011 at 6:34 PM, Torsten Wagner
wrote:
> The error message on export was correct to say
> org-export-latex-set-initial-vars: No definition for class
> `koma_article ' in `org-export-latex-classes' (again notice the space)
>
I can reproduce this with one of the default classes (art
batim}\n\n"))
2769a2776,2777
>
> ;; arch-tag: 23c2b87d-da04-4c2d-ad2d-1eb6487bc3ad
#+end_example
-Original Message-
From: emacs-orgmode-bounces+orgmode=cfraizer@gnu.org
[mailto:emacs-orgmode-bounces+orgmode=cfraizer@gnu.org] On Behalf Of
Nicolas Goaziou
Sent: Sunday, Octo
Hello,
"Colin Fraizer" writes:
> I have a file like this:
>
>
>
> * Item 1
>
> - list1a
>
> - list1b
>
> * Item 2
>
> - list2a
>
> *** TODO Test
>
> *** END
>
> - list2b
>
> * Item 3
>
>
>
> (1)If I export the whole file to LaTeX, everything works fine.
>
Hello,
Ilya Shlyakhter writes:
> org-archive-subtree calls (abbreviate-file-name (buffer-file-name))
> but the buffer file name is nil for indirect buffers.
I have committed a fix for that problem. If you have time, could you
confirm that it's working? Thanks.
Regards,
--
Nicolas Goaziou
58 matches
Mail list logo
