I updated to 7.5, recompiled, and now it works!
Thanks for the help!
On Wed, Mar 9, 2011 at 9:46 PM, Nick Dokos wrote:
> Rehan Iftikhar wrote:
>
>> I have tried adding
>>
>> #+TBLFM: @>$>=vmean(I..II)
>>
>> between the #+BEGIN and #+END lines (after generating a table), but
>> when I C-c C-c
>
> I have pushed a fix for this case. Thanks for your report, it reminds me
> filling in lists is still a bit fragile, and needs some care.
>
Thanks for the quick response! The list filling is very nice already.
Cheers,
Michael
That sounds like it means that any documents you might want to export to
LaTeX (and format with hard line breaks) should always have non-breaking
spaces after the periods---or you should keep a manual eye on your paragraph
formatting to make sure no numbers come first on the line.
Although I reall
Rehan Iftikhar wrote:
> I have tried adding
>
> #+TBLFM: @>$>=vmean(I..II)
>
> between the #+BEGIN and #+END lines (after generating a table), but
> when I C-c C-c on #+BEGIN, the table refreshes and removes the #+TBLFM
> line.
>
> I am using org-mode 7.4. Any idea why my formula isn't workin
John Hendy writes:
> I can't figure out what key combo provides "delete." Fn+delete behaves
> like backspace. In my searching, I found reference to C-?, but that
> comes up as unrecognized.
>
> How do I delete?
Try C-d. If that doesn't work, look at the help for delete-char (C-h f
delete-char )
I have tried adding
#+TBLFM: @>$>=vmean(I..II)
between the #+BEGIN and #+END lines (after generating a table), but
when I C-c C-c on #+BEGIN, the table refreshes and removes the #+TBLFM
line.
I am using org-mode 7.4. Any idea why my formula isn't working?
-Rehan
On Sat, Mar 5, 2011 at 12:48 A
I've run into a minor bug with cookie statistics.
The COOKIE_DATA property seems to break parent task statistics when it
is set to 'recursive'.
In the org file below task one/two/foo/a has the COOKIE_DATA property
set to recursive. Changing the state of task 'a' does not change the
statistics co
Hi,
I finally installed emacs/orgmode (using gnu emacs) on my OS X
partition (have had it on the Arch linux side) and have a probably
silly question. All has gone quite smoothly except for the fact that
for the life of me I can't figure out what key combo provides
"delete." Fn+delete behaves like
* lisp/org-clock.el (org-clock-in): Allow clocking in new tasks inserted
before the current clocking task
org-clock-in now checks that the name of the task you are clocking in
also matches org-clock-current-task. This allows us to insert a new
task in front of the current clocking task (with M-
* lisp/org-clock.el (org-clock-in): Set default clocking task when already
clocking the task
The default clocking task can now be set to the current clocking task.
Previously this just threw an error stating the clock continues in the
current clocking task. The double prefix now forces setting t
The following patch series fixes problems with with clocking in tasks and
setting the default clock task.
These patches are available at git://git.norang.ca/org-mode.git clock-fixes
Bernt Hansen (2):
Allow setting default clocking task to current clocking task
Allow clocking in new tasks ins
Markus Heller wrote:
> Debugger entered--Lisp error: (error ":END: line missing at position 15207")
> signal(error (":END: line missing at position 15207"))
> error(":END: line missing at position %s" 15207)
You seem to be missing an :END: line (or it may be malformed, so that the
regexp be
Hi Markus,
It looks like you have a drawer in your org files that is missing
a closing :END: tag. Possibly in file "h:/org/600_install.org"
HTH,
Bernt
Markus Heller writes:
> Nick Dokos writes:
>
>> Markus Heller wrote:
>>
>>> Hello group,
>>>
>>> I'm stumped. When I try to bring up the a
Nicolas writes:
> Hello,
>
> Matt Lundin writes:
>
>> A related bug:
>>
>>> - one
>>> - very, very, very, very, very, very, very, very, very, very, very,
>>> very, long
>>> - short
>>
>> If one calls unfill-paragraph on the "very, very" line above, nothing
>> happens. In the past, unfill pa
Hello,
Matt Lundin writes:
> A related bug:
>
>> - one
>> - very, very, very, very, very, very, very, very, very, very, very,
>> very, long
>> - short
>
> If one calls unfill-paragraph on the "very, very" line above, nothing
> happens. In the past, unfill paragraph would turn the item into
Hello,
michael hohn writes:
> after upgrading to the current git head (from a version around 6.36),
> fill-region produces wrong indentation for my lists. Starting with
>
> - one
> - very, very, very, very, very, very, very, very, very, very, very, very,
> long
> - short
>
> and marking th
Nick Dokos writes:
> Markus Heller wrote:
>
>> Hello group,
>>
>> I'm stumped. When I try to bring up the agenda with C-c a, I get the
>> error message mentioned in the subject line.
>>
>> I'm using 23.2.1 on Windoze 7 64 bit, and the orgmode from today:
>>
>> M-x org-version: 7.5
>>
>> Her
Markus Heller wrote:
> Hello group,
>
> I'm stumped. When I try to bring up the agenda with C-c a, I get the
> error message mentioned in the subject line.
>
> I'm using 23.2.1 on Windoze 7 64 bit, and the orgmode from today:
>
> M-x org-version: 7.5
>
> Here's my entire org-mode related par
Hello,
Stephen Eglen writes:
> With the following minimal org buffer:
>
> Simple test
>
> here here here here here here here here here here here here here here
> 2010. here here here here here here here here here here here here
> here here here here here here here here here here here here here
Hello group,
I'm stumped. When I try to bring up the agenda with C-c a, I get the
error message mentioned in the subject line.
I'm using 23.2.1 on Windoze 7 64 bit, and the orgmode from today:
M-x org-version: 7.5
Here's my entire org-mode related part of my .emacs:
,
| ;;
| ;; Org Mode
|
With the following minimal org buffer:
Simple test
here here here here here here here here here here here here here here
2010. here here here here here here here here here here here here
here here here here here here here here here here here here here here
when I export this to latex, I get:
Nick Dokos writes:
> Bernt Hansen wrote:
>
>> michael hohn writes:
>>
>> > Hi all,
>> >
>> > after upgrading to the current git head (from a version around 6.36),
>> > fill-region produces wrong indentation for my lists. Starting with
>> >
>> > - one
>> > - very, very, very, very, very, ver
Bastien writes:
> Hopefully this patch will solve a few issues that have just been raised
> about the new behavior of org-export-html-preamble/postamble.
With this patch, I get the following error when exporting to HTML:
list: Symbol's value as variable is void: creator-info
Bernt Hansen wrote:
> michael hohn writes:
>
> > Hi all,
> >
> > after upgrading to the current git head (from a version around 6.36),
> > fill-region produces wrong indentation for my lists. Starting with
> >
> > - one
> > - very, very, very, very, very, very, very, very, very, very, very,
michael hohn writes:
> Hi all,
>
> after upgrading to the current git head (from a version around 6.36),
> fill-region produces wrong indentation for my lists. Starting with
>
> - one
> - very, very, very, very, very, very, very, very, very, very, very, very,
> long
> - short
>
> and markin
Zhang Zhizhong wrote:
> I set up my capture template as follows:
> (setq org-capture-templates
> '(("t" "Todo" entry (file+headline "~/repo/org/refile.org" "Task")
> "* TODO %?\n %i%T\n %i%U\n %a\n" :clock-in t :clock-resume t)
> ("n" "Note" entry (file "~/repo/org/refile.org")
> "* %?\n %U\n %a
Hi,
On Wed, Mar 9, 2011 at 19:52, sakesun roykiattisak wrote:
> hi, I'm using color-theme-charcoal-black with org-mode on ntemacs-23.2.1.
> When I turn on column-view the view display in white background.
> Which make it very difficult to read.
> http://26.media.tumblr.com/tumblr_lhsnjosKkt1qhjuq
michael hohn writes:
> Hi all,
>
> after upgrading to the current git head (from a version around 6.36),
> fill-region produces wrong indentation for my lists. Starting with
>
> - one
> - very, very, very, very, very, very, very, very, very, very, very, very,
> long
> - short
>
> and markin
Hi Bastien,
On Wed, Mar 9, 2011 at 16:06, Bastien wrote:
> Aankhen writes:
>
>> This one seemed easy to fix, so I thought I’d butt in. :-) Hope the
>> format of the patch is right (I’m using hg-git).
>
> The patch was caught by patchwork, but wrongly wrapped.
>
> Thanks for it anyway!
Glad I co
Hi all,
after upgrading to the current git head (from a version around 6.36),
fill-region produces wrong indentation for my lists. Starting with
- one
- very, very, very, very, very, very, very, very, very, very, very, very, long
- short
and marking the second item via mark-paragraph follow
hi, I'm using color-theme-charcoal-black with org-mode on ntemacs-23.2.1.
When I turn on column-view the view display in white background.
Which make it very difficult to read.
http://26.media.tumblr.com/tumblr_lhsnjosKkt1qhjuqco1_400.png
How can I change the background color of column view ?
Or,
I set up my capture template as follows:
(setq org-capture-templates
'(("t" "Todo" entry (file+headline "~/repo/org/refile.org" "Task")
"* TODO %?\n %i%T\n %i%U\n %a\n" :clock-in t :clock-resume t)
("n" "Note" entry (file "~/repo/org/refile.org")
"* %?\n %U\n %a\n :CLOCK:\n :END:" :clock-in t :
Bastien wrote, On 3/9/2011 8:19 AM:
Bill Jackson writes:
In version 7.4, org-export-html-preamble and org-export-html-postamble
could be set to the name of a function that was passed an option plist.
See my last patch. It allows to set org-export-html-pre/postamble to a
function that will re
I had read this discussion thread (more than once!), but have not been
able to figure out how to accomplish what I was doing under 7.4 without
support for passing a function in org-export-html-preamble. I know how
to generate a preamble, but not how to generate one customized for each
.org sou
Hi all,
after upgrading to the current git head (version 7.xx, previously
6.36), fill-region produces wrong indentation for my lists. Starting
with
- one
- very, very, very, very, very, very, very, very, very, very, very,
very, long
- short
and marking the second item via mark-paragraph
I use beamer for presentations and appreciate the fine-grained control
over effects that it provides. For instance, I can combine overlay
specifications with includegraphics to mix and match different text and
images on the same frame.
--8<---cut here---start->8
Thanks -- you guys rock!
-- Gary
At Sat, 05 Mar 2011 10:14:17 +0100,
Bastien wrote:
Hello Bastien,
Sorry for the late reply. For some reason (path related) Emacs was loading
an older version of org instead of the one from git and I wasn't seeing your
changes.
>
> Hi Darlan,
>
> Darlan Cavalcante Moreira writes:
>
> > I knew
Hi Gary,
Gary Oberbrunner writes:
> One question: I'm using the new export stuff from org-jambu (git
> master branch); any idea when Jambunathan will rebase or merge with
> this?
The plan is to work together on this and try to have something merged
for the next release. But devil is in the det
Bastien wrote:
> Hi Brenton,
>
> Brenton Kenkel writes:
>
> > I am having a problem with exporting to LaTeX from org-mode. I am
> > running org-mode 7.5 in Emacs 23.1.1 on 64-bit Ubuntu 10.10.
>
> I cannot reproduce it -- can you test with a bare emacs -q ?
>
> Also, please make sure to rem
Indeed, congrats to Bastien and all!
One question: I'm using the new export stuff from org-jambu (git
master branch); any idea when Jambunathan will rebase or merge with
this?
Hi Brenton,
Brenton Kenkel writes:
> I am having a problem with exporting to LaTeX from org-mode. I am
> running org-mode 7.5 in Emacs 23.1.1 on 64-bit Ubuntu 10.10.
I cannot reproduce it -- can you test with a bare emacs -q ?
Also, please make sure to remove any previous Org installation.
B
I am having a problem with exporting to LaTeX from org-mode. I am
running org-mode 7.5 in Emacs 23.1.1 on 64-bit Ubuntu 10.10. (I am using
the stable version, but the same error occurs when I use the development
version from git.) When I run "C-c C-e d", I receive the error message
"Cannot open
The attached patch makes tangling (org-babel-tangle) work
in indirect buffers. Previously it would fail before running
org-babel-post-tangle-hook because indirect have a buffer-file-name
of nil whereas the code was expecting a string in the following
fragment:
(message "tangled %d code block%s fr
Hopefully this patch will solve a few issues that have just been raised
about the new behavior of org-export-html-preamble/postamble.
`org-export-html-preamble' defaults back to `t', to reproduce the
previous default behavior.
`org-export-html-postamble' default to 'auto -- which mean that
org-ex
Hi Bill,
Bill Jackson writes:
> In version 7.4, org-export-html-preamble and org-export-html-postamble
> could be set to the name of a function that was passed an option plist.
See my last patch. It allows to set org-export-html-pre/postamble to a
function that will return a string. The funct
Hi Jason,
Jason Dunsmore writes:
> Is this a bug? It makes sense to me that #TITLE: would add an page
> heading with or without :html-preamble being defined.
Yes, there are still problems in this area -- see my last patch and tell
me if this does things right for you.
Best,
--
Bastien
I'm a little late, but thanks to Bastien and everyone involved, and
congratulations on the release!
Best,
At Mon, 07 Mar 2011 15:42:19 +0100,
Bastien wrote:
>
> Dear all,
>
> here it is, release 7.5, my first release as Org's new maintainer.
>
> This release comes with lots of new features, bu
Bastien writes:
>> Also, I have no title when I set the title with "#+TITLE: " on the first
>> line. I'm not sure if this has to do with org-export-html-title-format
>> being removed.
>
> Mhh.. I cannot reproduce this. Can you check again?
I was mistaken. It was exporting a . However, it was
Aankhen wrote:
> FWIW, same here. Firefox 3.6.15 on Windows 7. Given that both pages
> specify the MathJax_Math font yet only mathjax.org actually looks like
> it uses it, you’re probably right about MathJax having trouble finding
> the fonts on yours.
>
> I tried a couple other browsers. IE
I use org-mode with pyBlosxom, though I haven't posted anything for a month
of Sundays.
I don't use org-mode to maintain the blog, only to compose. Generally, I
just export a subtree to HTML and save that in a folder that pyBlosxom knows
about. The only catch is the need to strip the id attributes
Hi Manuel,
Manuel Giraud writes:
> Bastien writes:
>
>> Bastien writes:
>>
>>> May I ask you to rewrite these patches into a single one?
>>
>> PS: I mean: merge all patches in this thread relevant to the problem,
>> possibly including Aankhen patch. Thanks!
>
> Ok, here it is. Hopes this one'
Patch 664 (http://patchwork.newartisans.com/patch/664/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C87fwqwnxj6.fsf%40univ-nantes.fr%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8
> On Wed, 09 Mar 2011 11:46:50 +, Eric S Fraga said:
ESF> Are you intending to extend your code for not-so-appropriate fields? If
ESF> so, I definitely would like to see the addresses converted and it would
ESF> be quite useful to have the notes converted entry text for the org entry
ESF
Bastien writes:
> Bastien writes:
>
>> May I ask you to rewrite these patches into a single one?
>
> PS: I mean: merge all patches in this thread relevant to the problem,
> possibly including Aankhen patch. Thanks!
Ok, here it is. Hopes this one's ok.
>From a9e692243b37be9947db9a7220ea561d261
Hi Sébastien,
Sébastien Vauban writes:
>> Thanks for catching this -- I've applied a modified patch, yours add
>> EXPORT_DATE twice :)
>
> Hein? Not sure what you're talking about...
I'm talking about _nothing_ -- just misread your patch.
Sorry for that!
--
Bastien
Hi Bernt,
Bernt Hansen writes:
> I don't think your version is correct. The original patch added
> EXPORT_TEXT and EXPORT_DATE (not EXPORT_DATE twice) and your version is
> missing EXPORT_TEXT.
Right, I just fixed this...
--
Bastien, who gets a bit of a post-release hang-over
Bastien writes:
> Hi Sébastien,
>
> Sébastien Vauban writes:
>
>> I found out about (at least) 2 missing "known" properties. This patch
>> adds them to the list.
>
> Thanks for catching this -- I've applied a modified patch, yours add
> EXPORT_DATE twice :)
>
> Best,
Hi Bastien,
I don't think
Here is the the configuration I run
(defun turn-on-full-org-mailing ()
(turn-on-orgstruct++)
(turn-on-orgtbl)
(load "org-html-mail"))
(add-hook 'mail-mode-hook 'turn-on-full-org-mailing)
in order make use of Org minor mode (struct, tbl) within mail-mode.
Unfortunately with
Hi Bastien,
Bastien wrote:
> Sébastien Vauban writes:
>
>> I found out about (at least) 2 missing "known" properties. This patch
>> adds them to the list.
>
> Thanks for catching this -- I've applied a modified patch, yours add
> EXPORT_DATE twice :)
Hein? Not sure what you're talking about...
Wes Hardaker writes:
> I finally decided to take a wack at a bbdb to org-contacts converter.
> I'm attaching the file below. It should prompt for a file and
> insert all your existing bbdb records into the file using the formats
> and fields that I decided was appropriate ;-)
Thanks. This seem
Matt Lundin writes:
> The following patch fixes the sorting bug. It also inserts a blank line
> above a new footnote definition, which is consistent with the spacing
> that results when sorting footnotes.
Applied, thanks.
--
Bastien
Patch 658 (http://patchwork.newartisans.com/patch/658/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C8762rul8xr.fsf%40fastmail.fm%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
>
Bastien writes:
> May I ask you to rewrite these patches into a single one?
PS: I mean: merge all patches in this thread relevant to the problem,
possibly including Aankhen patch. Thanks!
--
Bastien
Hi Manuel,
Manuel Giraud writes:
> Thanks. Modulo line breakage this patch applies and Jambunathan's test
> file now validates XHTML 1.0
>
> Here's the 2 patch that solve this:
Thanks for the patches -- patchwork can only catch *one* patch per mail.
I guess that's because people are encouraged
Hi Aankhen,
Aankhen writes:
> This one seemed easy to fix, so I thought I’d butt in. :-) Hope the
> format of the patch is right (I’m using hg-git).
The patch was caught by patchwork, but wrongly wrapped.
Thanks for it anyway!
--
Bastien
Manuel Giraud writes:
> Ok this one was easy. Here's a patch that correct the body-only
> behaviour.
Thanks for this!
--
Bastien
Patch 662 (http://patchwork.newartisans.com/patch/662/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C87fwqx3csc.fsf%40univ-nantes.fr%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8
Hi Sébastien,
Sébastien Vauban writes:
> I found out about (at least) 2 missing "known" properties. This patch
> adds them to the list.
Thanks for catching this -- I've applied a modified patch, yours add
EXPORT_DATE twice :)
Best,
--
Bastien
Hi Jason,
I finally had a chance to better understand what your patch does and
fix. I've applied it now -- thanks for it and for your patience!
--
Bastien
Patch 617 (http://patchwork.newartisans.com/patch/617/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C878vxhgsyy.fsf%40riotblast.dunsmor.com%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset
Hi David,
David Maus writes:
> What if BODY inserts or deletes characters inside the narrowed region?
> In this case the upper boundary of the region is no longer (point-max)
> before executing body. Thus the buffer might be narrowed to the wrong
> region after executing body. No, wait: If BODY
Hi Carsten,
Carsten Dominik writes:
> (defmacro org-with-wide-buffer (&rest body)
> "Execute body while temporarily widening the buffer."
> `(save-excursion
> (save-restriction
>(widen)
>,@body)))
Err... of course. Stupid me. Thanks for looking into this and for the
fix
On Tue, Mar 08 2011, Michael Käufl wrote:
> Q1) links to contacts
> Is there a common way to create links to contacts?
I'd say just the same way as for any Org entry.
> F1) csv export
> When writing bulk letters with LaTeX, all I need is a file with the
> recipients addresses in some predefined
74 matches
Mail list logo
