Hi Eric,
> I personally don't have time to make these changes right now, but I'd be
> happy to provide guidance and answer questions to anyone who wanted to
> try to submit a patch. Also, there are a number of files which can
> serve as examples of how to compile and execute code with Babel e.g.,
Hi,
is anyone interested in giving a blistering talk about org-mode at the
Snow headquarters in the Netherlands (the town of Geldermalsen)?
Our original plan to have someone talk about hacking DECT and other
protocols had to be postponed.
The public consists of about 80 Unix and Security Specialis
On Mon, Aug 22 2011, Sebastien Vauban wrote:
> Hi Eric,
>
> Eric Abrahamsen wrote:
>> On Mon, Aug 22 2011, Bernt Hansen wrote:
>>
>>> Eric Abrahamsen writes:
>>>
What would it take to get an Agenda tags view that indented nested
TODOs? I've always been bothered by the fact that nested T
Hi,
here is an example that delivers an error "reference 'table1' not
found in this buffer" when trying to export to HTML (others not tried
yet):
#+tblname: table1 :noexport:
| n | x | y1 | y2 |
|---+---+-+--|
| 0 | 1 | 2.0 | 3.0 |
| 1 | 2 | 2.1 | 2.0 |
| 2 | 3 | 2.
Hi András & al.,
András Major wrote:
> here is an example that delivers an error "reference 'table1' not
> found in this buffer" when trying to export to HTML (others not tried
> yet):
>
> #+tblname: table1 :noexport:
> | n | x | y1 | y2 |
> |---+---+-+--|
> | 0 | 1 | 2.0
Hi Sebastian,
> I will let answer the ones who decide on such things. Though, I am amazed you
> put a tag on the table itself.
>
> I'd have expected the noexport tag to be on a section containing the table.
I forgot to mention in the report that of course I tried that too: if
I place the table a
Hi,
Yet another one I just stumbled across: if I create a table and use
"!" in the first column to assign names to the columns, I can only
reference those columns by name in #+TBLFM: if the names don't contain
a "_" character. This isn't mentioned in the docs and shouldn't be
so, IMHO. I haven't
András Major wrote:
> Yet another one I just stumbled across: if I create a table and use
> "!" in the first column to assign names to the columns, I can only
> reference those columns by name in #+TBLFM: if the names don't contain
> a "_" character. This isn't mentioned in the docs and shouldn
> Try adding an underscore to the regexp on line 2179 of org-table.el -
> something like this (untested):
>
> ...
> (if (string-match "^[a-zA-Z][a-zA-Z0-9_]*$" name)
> (push (cons name (int-to-string cnt)) org-table-column-names
>
> The only characters permitted
On Aug 23, 2011, at 3:53 PM, Nick Dokos wrote:
> András Major wrote:
>
>
>> Yet another one I just stumbled across: if I create a table and use
>> "!" in the first column to assign names to the columns, I can only
>> reference those columns by name in #+TBLFM: if the names don't contain
>> a "
Carsten Dominik wrote:
>
> On Aug 23, 2011, at 3:53 PM, Nick Dokos wrote:
>
> > András Major wrote:
> >
> >
> >> Yet another one I just stumbled across: if I create a table and use
> >> "!" in the first column to assign names to the columns, I can only
> >> reference those columns by name in
Hello,
I am using the excellent org-odt, so thanks to Jambunathan K, and
everyone who has ever contributed to orgmode.
This may be quite simple so I am asking before making an minimal
example. Does anyone know how to cause a label such as "Figure 1." in
the odt (for the resulting png), and set
András Major writes:
> Hi,
>
> here is an example that delivers an error "reference 'table1' not
> found in this buffer" when trying to export to HTML (others not tried
> yet):
>
> #+tblname: table1 :noexport:
> | n | x | y1 | y2 |
> |---+---+-+--|
> | 0 | 1 | 2.0 | 3.0
András Major writes:
> Hi Eric,
>
>> I personally don't have time to make these changes right now, but I'd be
>> happy to provide guidance and answer questions to anyone who wanted to
>> try to submit a patch. Also, there are a number of files which can
>> serve as examples of how to compile and
Bastien writes:
> Hi Jason,
>
> Jason Dunsmore writes:
>
>> I ran some tests and found that the download speed is proportional to
>> the size of the repo:
>
> Good to know, thanks.
>
>> If you clone via git://, it does some optimizations during the transfer,
>> whereas cloning via http:// does n
On Thu 2011-08-18 at 19:09, Bastien wrote:
> Hi Jon,
>
> Jon Anders Skorpen writes:
>
> > I have made a function which creates a blog-like sitemap. It works as
> > an alternative sitemap function to org-publish.
>
> This looks very interesting -- do you have a webpage we can look at to
> see t
On Aug 23, 2011, at 4:32 PM, Nick Dokos wrote:
> Carsten Dominik wrote:
>
>>
>> On Aug 23, 2011, at 3:53 PM, Nick Dokos wrote:
>>
>>> András Major wrote:
>>>
>>>
Yet another one I just stumbled across: if I create a table and use
"!" in the first column to assign names to the col
Hi Eric,
> This is the first time I've seen a tag applied to a table. I've updated
> the results regular expression so that it will now admit examples like
> yours above. Please let me know if this doesn't work with the latest
> Org-mode.
That's good news! Well, the bad news is that it doesn't
András Major writes:
> Hi Eric,
>
>> This is the first time I've seen a tag applied to a table. I've updated
>> the results regular expression so that it will now admit examples like
>> yours above. Please let me know if this doesn't work with the latest
>> Org-mode.
>
> That's good news! Well
Hi Eric,
> > That's good news! Well, the bad news is that it doesn't work. I've
> > just pulled the current version (release_7.7.174.g63fae) and now the
> > behaviour is different:
> >
> > - :noexport: in the #+tblname: has no effect.
>
> I'm not sure that it is legal to apply tags to tables, s
Hi András,
András Major writes:
> here is an example that delivers an error "reference 'table1' not
> found in this buffer" when trying to export to HTML (others not tried
> yet):
>
> #+tblname: table1 :noexport:
> | n | x | y1 | y2 |
> |---+---+-+--|
> | 0 | 1 | 2.0 |
Hi András,
András Major writes:
> Thanks Nick. It would be nice if the documentation reflected such an
> arbitrary choice of characters you can use...
I added a footnote.
--
Bastien
Hi András,
András Major writes:
>> I'd have expected the noexport tag to be on a section containing the table.
>
> I forgot to mention in the report that of course I tried that too: if
> I place the table and the code in two sections and tag the section
> containing the table with :noexport:, th
Hi Thomas,
t...@tsdye.com (Thomas S. Dye) writes:
> Thanks for adding this. I work with literal links and this potentially
> saves time and effort.
>
> I wonder if I'm using it correctly? In .emacs I set
> org-link-display-descriptive nil and have:
>
>
> org-link-display-descriptive is
Hi Nick,
Nick Dokos writes:
> Try adding an underscore to the regexp on line 2179 of org-table.el -
> something like this (untested):
>
> ...
> (if (string-match "^[a-zA-Z][a-zA-Z0-9_]*$" name)
> (push (cons name (int-to-string cnt)) org-table-column-names
>
> T
Matt Lundin writes:
> Matt Lundin writes:
>
>> Since the commit c25165c25dc9fdb5b57b3c66b2e0ec0efdbeb7ad on August 18,
>> I can only call this function when I am beneath the first level heading
>> of an org-mode file. Otherwise I receive the following error:
>
> Here's a patch that allows one to
Hi Eric,
Eric Schulte writes:
> I'm not sure that it is legal to apply tags to tables, so I'm not sure
> if this is a bug.
I confirm tags are for headlines only.
If we want to add more export options to tables, let's use the usual
"#+[option] syntax -- like #+caption does.
--
Bastien
Hi András,
András Major writes:
> I think that anything that works despite being designed and documented
> otherwise is confusing to the user and should be considered a bug.
> I'm happy that it no longer works and hope that it stays that way.
I think tags are clearly documented as being propert
Michael Brand writes:
> If the shell is a special case for babel anyway, why not something
> like the following?
Ehm, no. But I think that it would be generally useful (not just for
shell blocks) to be able to capture stderr, either together with stdout
or separately into a result target block a
Hi Carsten,
Carsten Dominik writes:
>> The only characters permitted are alphanumerics. That can probably be
>> easily relaxed.
>
> Hi Nick, I don't think it can be easily relaxed. Many other characters are
> operators in Calc and would lead to confusion.
So perhaps my recent commit is wrong.
Hi Peter,
Peter Frings writes:
> Yes, I did. I did find the offending command. Hooray!
Great -- thanks for sharing!
> (setq org-replace-disputed-keys t)
>
> Was set in the init.el file of the starter-kit.
>
> Now, is it just me or is the relation between this variable and
> ‘org-support-shift
Nick Dokos writes:
> The only characters permitted are alphanumerics. That can probably be
> easily relaxed.
Only if you don't want to have _underlined_ still working and perhaps
never use calc on that table. The problem with simple syntax is that
the quoting rules become bizarre and the other w
Eric Schulte writes:
> It will probably be a couple of days before I have sufficient time to
> address these issues, but rest assured it is only my TODO list.
Thanks for your persistence in fixing this!
--
Bastien
Jason Dunsmore writes:
>> Okay -- can you "git gc" on the server?
>
> Okay, done:
Great -- thanks a lot!
--
Bastien
On 23.8.2011, at 18:20, Bastien wrote:
> Hi Carsten,
>
> Carsten Dominik writes:
>
>>> The only characters permitted are alphanumerics. That can probably be
>>> easily relaxed.
>>
>> Hi Nick, I don't think it can be easily relaxed. Many other characters are
>> operators in Calc and would lea
Bastien writes:
> Hi Thomas,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Thanks for adding this. I work with literal links and this potentially
>> saves time and effort.
>>
>> I wonder if I'm using it correctly? In .emacs I set
>> org-link-display-descriptive nil and have:
>>
>>
>>
Achim Gratz writes:
> Michael Brand writes:
>> If the shell is a special case for babel anyway, why not something
>> like the following?
>
> Ehm, no. But I think that it would be generally useful (not just for
> shell blocks) to be able to capture stderr, either together with stdout
> or separa
Michael Brand writes:
> Hi Eric
>
> 2011/8/20 Eric Schulte :
>> [...] I would lean towards thinking
>> that passing along error messages is more important than returning error
>> codes, but if the community thinks differently I'm happy to change the
>> ob-sh behavior.
>
> A non-zero exit status a
>
> Your file uses #+data: where I use #+tblname: -- which one is the
> official one? I have the impression that it's #+data:, but I haven't
> come across that in the manual or elsewhere before. If #+tblname:
> isn't supposed to be used as a target for a variable in the code
> block, then we shou
Hi all,
I wasn't able to google a clear examples of how to do this. For
example, I'd like to highlight all text between double-quotes.
--
Le
sort of hijacking this thread with a quick note:
In order to remove numbering from the headings produced by org-odt,
simply export a file, go to Tools -> Outline Numbering in
libreoffice/openoffice, and turn numbering off for levels 1-10
(probalby you only need about 4 levels anyway). Then save t
On 23.8.2011, at 18:20, Bastien wrote:
> Hi Carsten,
>
> Carsten Dominik writes:
>
>>> The only characters permitted are alphanumerics. That can probably be
>>> easily relaxed.
>>
>> Hi Nick, I don't think it can be easily relaxed. Many other characters are
>> operators in Calc and would lea
Here is a different solution. It is from my notes from long ago.
To me, one issue with indenting is that you expect the previous line
to be a direct parent, analogously with the outline. This conflicts
with sorting and non-child descendents.
If you sort, you can't take advantage of the feature
Carsten Dominik writes:
> I have checked, underscore is aceptable, calc allows it in variables
> names. However, I would not recommend adding any more characters to
> this regexp.
Thanks for the quick feedback!
--
Bastien
Hi Eric,
Bastien writes:
>> I think this fix is causing some mischief.
>
> I reverted this commit -- let's wait Eric is back and can fix this with
> a better solution.
Eric -- just making sure this is under your radar.
I reverted your fix because it was not answering Thomas' problem,
but it
Bastien writes:
> Hi Eric,
>
> Bastien writes:
>
>>> I think this fix is causing some mischief.
>>
>> I reverted this commit -- let's wait Eric is back and can fix this with
>> a better solution.
>
> Eric -- just making sure this is under your radar.
>
Thanks, I had lost track of the end of t
t...@tsdye.com (Thomas S. Dye) writes:
> Eric Schulte writes:
>
>> t...@tsdye.com (Thomas S. Dye) writes:
>>
>>> Aloha all,
>>>
>>> I'm trying, partially successfully, to configure org-bibtex so it mimics
>>> some useful features of ebib. In particular, I'm wanting to add several
>>> optional fi
Commit 08ca5be491f5704cc0c6cb87013a5e8537218488 causes an error because
of typo: i.e., "point-maker" instead of point-marker
Best,
Matt
Hi Bastien,
> I'm not sure I understand -- does it mean that C-cC-c on #+begin_src
> fails in the example below?
No, it means that exporting to HTML fails with that error message. It
should actually evaluate the code and include the resulting PNG in the
output (and that's what it does when :noe
Hi Bastien,
> > I think that anything that works despite being designed and documented
> > otherwise is confusing to the user and should be considered a bug.
> > I'm happy that it no longer works and hope that it stays that way.
>
> I think tags are clearly documented as being properties of the
>
Hi Eric,
> > Your file uses #+data: where I use #+tblname: -- which one is the
> > official one? I have the impression that it's #+data:, but I haven't
> > come across that in the manual or elsewhere before. If #+tblname:
> > isn't supposed to be used as a target for a variable in the code
> > b
András Major wrote:
> Hi Eric,
>
> > > Your file uses #+data: where I use #+tblname: -- which one is the
> > > official one? I have the impression that it's #+data:, but I haven't
> > > come across that in the manual or elsewhere before. If #+tblname:
> > > isn't supposed to be used as a targe
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Eric Schulte writes:
>>
>>> t...@tsdye.com (Thomas S. Dye) writes:
>>>
Aloha all,
I'm trying, partially successfully, to configure org-bibtex so it mimics
some useful features of ebib. In particular, I'm want
Matt
> sort of hijacking this thread with a quick note:
>
> In order to remove numbering from the headings produced by org-odt,
> simply export a file, go to Tools -> Outline Numbering in
> libreoffice/openoffice, and turn numbering off for levels 1-10
> (probalby you only need about 4 levels anyw
Detlef
> Will you take care of org-odt working in orgmode for the foreseeable
> future or don`t you care about orgmode anymore?
I pushed a commit just a few minutes ago. So things are back to normal.
Jambunathan K.
András Major writes:
> Hi Bastien,
>
>> > I think that anything that works despite being designed and documented
>> > otherwise is confusing to the user and should be considered a bug.
>> > I'm happy that it no longer works and hope that it stays that way.
>>
>> I think tags are clearly document
Nick Dokos writes:
> András Major wrote:
>
>> Hi Eric,
>>
>> > > Your file uses #+data: where I use #+tblname: -- which one is the
>> > > official one? I have the impression that it's #+data:, but I haven't
>> > > come across that in the manual or elsewhere before. If #+tblname:
>> > > isn't
Hi Bastien and everyone,
I wanted to implement a history facility for sparse trees. Since sparse
trees use org-occur and org-scan-tags any such facility would need to
be aware of both functions. My lisp foo proved to be too weak to
understand org-scan-tags, so I implemented this only for org-occur
Hello,
Matt Lundin writes:
> Commit 08ca5be491f5704cc0c6cb87013a5e8537218488 causes an error because
> of typo: i.e., "point-maker" instead of point-marker
Fixed, thanks.
--
Nicolas Goaziou
Eric Schulte writes:
> Nick Dokos writes:
>
>> András Major wrote:
>>
>>> Hi Eric,
>>>
>>> > > Your file uses #+data: where I use #+tblname: -- which one is the
>>> > > official one? I have the impression that it's #+data:, but I haven't
>>> > > come across that in the manual or elsewhere bef
> I personally would really like to see important contribution such
> as yours become more and more integrated into the 'standard'
> Org ditribution - and not pushed further away.
Precisely my point. Bastien's idea of merge is to make it into a long
drawn affair. I disagree.
Jambunathan K.
> Le Wang writes:
> I wasn't able to google a clear examples of how to do this. For example,
> I'd like to highlight all text between double-quotes.
Typically it looks something like this:
(font-lock-add-keywords org-mode
(list (list (concat "\\(\"[^\"]+\"\\)")
> Precisely my point. Bastien's idea of merge is to make it into a long
> drawn affair. I disagree.
It would help if you or Bastien could explain what is going on. As is
clear, everyone is hoping that the issues will be resolved and your
valuable contributions will remain a part of org-mode.
It
> John Wiegley writes:
> Le Wang writes:
>> I wasn't able to google a clear examples of how to do this. For example,
>> I'd like to highlight all text between double-quotes.
> Typically it looks something like this:
> (font-lock-add-keywords org-mode
[...]
Sorry, that should be 'or
Thanks for the hint, I tried this, but all my beautiful salad bowl
colours went away.
(font-lock-add-keywords 'org-mode '(("\"\\(\\(?:.\\|\n\\)*?[^\\]\\)\""
0 font-lock-string-face)))
Notice that I made a bad attempt to handle escaped quotation mark in
the string. Does anyone know a better solut
Log
[[[
* lisp/org-agenda.el
(org-agenda-get-todos): Set category-pos before usage.
]]]
Thanks and Regards
Noorul
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index e3236e5..8d869be 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -4607,6 +4607,7 @@ the documentation of `org-
> Hi Jambunathan,
>
>> I have made a decision not to merge org-lparse, org-xhtml & org-odt in
>> to Orgmode core. It is a very difficult decision for me to take
>> considering that I had put all my heart in to it. (Btw, this decision
>> has nothing to with me not having enough time at hand.)
>
>
Hi Tom,
> > To me, the documentation is the leading specification of a piece of
> > software. Anything the software doesn't do that is in the docs is a
> > bug, but likewise anything it does do which the docs don't cover is
> > also a bug.
>
> Aloha Andras,
>
> As an avocational programmer who
> It does seem that you are, for now, letting them be within org-mode
> (your other mail). But it would still help if you express your
> apprehensions and discuss them openly on this list.
There is another mail that is on it's way. (Replies to Sebastien Vauban
always appear longer time to appear
69 matches
Mail list logo
