At Wed, 02 Nov 2011 19:28:52 -0400,
Nick Dokos wrote:
>
> i...@bastianebeling.org wrote:
>
> > > Hi All,
> > >
> > > I'm trying to set up MobileOrg to try it out, but I'm getting the
> > > following error when I run org-mobile-push:
> > >
> > > byte-code: Invalid function: org-eval-in-environment
Dear Samuel,
I like the way you frame the issue and the solution you
are sketching.
I am not fund of a "dedicated top-level entry for all
file-level control purposes" because it transforms the
ambiguity about keywords' scope into an ambiguity about
structure: IMHO a subtree should never be so
Hi Nick,
Nick Dokos writes:
> With this information, do you think you could get a patch together?
I hope Sten will be able to provide a patch!
> Let me know if you have questions.
Thanks for the detailed analysis.
> Footnotes:
>
> [fn:1] For legal reasons, I cannot fix it myself.
Com'on Nic
Hi Carsten,
Carsten Dominik writes:
> OK, I will take a look at it and then push.
Great, thanks!
>> - From the docstring: "[...] or add in the middle or right after an
>> invisible region" -- I agree inserting while in the middle of the
>> invisible region would feel too unpredictable, but I
Hi Brian,
Brian Wightman writes:
> Given that a common recommendation for a bug fix is to 'try commit
> blah blah blah', would it make sense to have bug fixes go onto a
> 'maint' branch (as well as master), and new features / changed
> features stay on the master branch?
Yes, this makes sense
Hi Andrew,
Andrew Hyatt writes:
> Would anyone be interested in the ability to archive to the current
> date in date-tree instead of an archive file? I'm toying with the
> idea of implementing this, and I could send it in as a patch when it
> is done, or just leave it as a personal module if no
Hi Nicolas,
Nicolas Goaziou writes:
> For the sake of consistency, I would suggest to drop the export back-end
> relative keywords. "#+html:" and "#+latex:" are indeed disturbing
> exceptions to the rule. They are also not so convenient (a net gain of
> 2 lines).
Why not. But let's not break b
i...@bastianebeling.org wrote:
>
> Am 03.11.2011 um 00:28 schrieb Nick Dokos:
>
> > i...@bastianebeling.org wrote:
> >
> >>> when I run org-mobile-push:
> >>>
> >>> byte-code: Invalid function: org-eval-in-environment
> >>
> > org-eval-in-environment is a macro defined in org-macs.el and ma
I just formally pushed up a new version of VimOrganizer, an Org clone in Vim.
This version is much closer to being a true alternative to using Org-mode in
Emacs. I say alternative to "using Org-mode in Emacs", because VimOrganizer in
large part operate as a front end to Org-mode by making calls t
Am 03.11.2011 um 00:28 schrieb Nick Dokos:
> i...@bastianebeling.org wrote:
>
>>> when I run org-mobile-push:
>>>
>>> byte-code: Invalid function: org-eval-in-environment
>>
> org-eval-in-environment is a macro defined in org-macs.el and macros
> sometimes cause problems with compiled code un
On Wed, 02 Nov 2011 19:11:38 -0400, Nick Dokos wrote:
> They are generally called (somewhat misleadingly) diary sexps - they are
> executed by org-agenda-get-sexps (assuming that they are in some agenda
> file) when the agenda is constructed, once for every day displayed: they
> do their things an
i...@bastianebeling.org wrote:
> > Hi All,
> >
> > I'm trying to set up MobileOrg to try it out, but I'm getting the
> > following error when I run org-mobile-push:
> >
> > byte-code: Invalid function: org-eval-in-environment
>
>
> Hi,
>
> I have the same problem and get the same error messa
Daniel Schoepe wrote:
> Hello,
>
> I'm trying to dynamically generate a list of TODO entries (specifically,
> a list of notmuch[1] threads that have a "todo" tag) that I'd like to
> see in the TODO agenda, but not in the normal daily agenda (just like a
> ordinary TODO entry without a date). A s
> Hi All,
>
> I'm trying to set up MobileOrg to try it out, but I'm getting the
> following error when I run org-mobile-push:
>
> byte-code: Invalid function: org-eval-in-environment
Hi,
I have the same problem and get the same error message. My only fix is to hit
C-u C-c C-x r (reload Org un
>> On Wed, 02 Nov 2011 00:44:57 +0530, Jambunathan K said:
>> 2. mathml - You need to register your command file with -ncf
>> argument.
>>
>> For example, if I put the mystyle.tex in the same directory as
>> exported .org file and add the -ncf argument to the converter as
>> below
>
>> On Wed, 02 Nov 2011 23:51:31 +0530, Jambunathan K said:
>> >> There is (git from a couple of days ago) a problem with referring
>> >> to equations containing an underscore in the label, I am fairly
>> >> sure it was allowed before, e.g.:
>> >>
>> >> #+LABEL: Equation:new_eq \begin{eq
Hello,
I'm trying to dynamically generate a list of TODO entries (specifically,
a list of notmuch[1] threads that have a "todo" tag) that I'd like to
see in the TODO agenda, but not in the normal daily agenda (just like a
ordinary TODO entry without a date). A simple try like
(defun foo ()
"Tes
A followup on my second point.
On 2011-11-02, Samuel Wales wrote:
> ===
>
> One interesting possibility is to have a dedicated top-level
> entry for all file-level control purposes. Then it's clear
> where everything should go, and syntax can even follow the
> subtree syntax.
Thus, for example,
Something that has not been mentioned yet, as a possible
background.
One nice thing about subtrees (the properties drawer) for
control is that they are nicely (essentially lexically)
scoped and nested as in many programming languages.
One issue with blocks for control is that they are
ambiguously
On Tue, 01 Nov 2011 11:17:51 +0100, Sandra Snan wrote:
> What I want is that if I look at my list of things to do, and I’ve
> already swept the floor and marked it as done, it shouldn’t bother me
> anymore for the day, but pop up the next day. And if I’ve swept the
> floor, I’ll be presented with
Am 01.11.2011 21:05, schrieb Jambunathan K:
The location of the elisp file is:
http://ferntreffer.de/elisp/org-refer-by-number.el
Copyright line says it is FSF. In that case, you should consider adding
it to GNU ELPA - http://elpa.gnu.org
Thanx for the suggestion; I will try !
re
>> >> There is (git from a couple of days ago) a problem with referring
>> >> to equations containing an underscore in the label, I am fairly
>> >> sure it was allowed before, e.g.:
>> >>
>> >> #+LABEL: Equation:new_eq \begin{equation} x=\sqrt{b} \end{equation}
>> >>
>> >> Referrin
Marcelo de Moraes Serpa writes:
> A bit off topic but related I think...
[...]
> Do you guys ever encrypt your emails? I must say I never did, but it
> doesn't sound bad for sensitive data, and if you have a business and or
> need to deal with services that require your business or personal doc
Ian Barton writes:
> On 02/11/11 13:13, Nick Dokos wrote:
>> Ian Barton wrote:
>>
>
>>> If I have a large begin_src block it can make reading the surrounding
>>> text difficult, as the reader has to keep paging up and down. Ideally
>>> it would be possible to fold src blocks, but I can see that
Hello,
Bastien writes:
> 1) Consistent syntax for #+xxx and #+begin_xxx?
>
>Nicolas point is valid -- #+begin_xxx syntax is about content and
>formatting, not about Org's internal. #+xxx is mostly about Org's
>internals (#+author, #+date, #+property, etc) and sometimes about
>co
Robert McIntyre writes:
> In my literate org projects at http://aurellem.com/, I often have to
> use very long lines such as:
>
> #+description: Capture video from a JMonkeyEngine3 Application with
> Xuggle, and use gstreamer to compress the video to upload to YouTube.
>
> #+begin_src clojure :no
Hi all
When the :id for a columview of a dynamic block references to a sub
tree with the property ID there is an issue if that tree is in
overview (closed): The whole tree of the top level parent of the
requested ID is included in the resulting table.
When the minimal and complete example below i
Hi all
There are some issues with dynamic block for columnview. Attached are
four minimal and complete example test files indent*_tbl*.org (remove
.txt) with different wrong behaviors dependent on if the dynamic block
is indented and if there is already a table from a previous update or
not. The t
Hi All,
I'm trying to set up MobileOrg to try it out, but I'm getting the
following error when I run org-mobile-push:
byte-code: Invalid function: org-eval-in-environment
Here is my minimal .emacs file:
(setq load-path (cons "~/elisp/org-mode/lisp/" load-path))
(global-set-key "\C-ca" 'org-age
Dear all,
here is my take on this issue.
First of all, sorry that the #+begin_property caused confusion,
I'm the one responsible as I suggested this suggestion to Eric.
I can see three issues:
1) Consistent syntax for #+xxx and #+begin_xxx?
Nicolas point is valid -- #+begin_xxx syntax is a
Myles English wrote:
>
> Nick,
>
> >> On Wed, 02 Nov 2011 09:38:20 -0400, Nick Dokos said:
>
> > Myles English wrote:
> >>
> >> There is (git from a couple of days ago) a problem with referring
> >> to equations containing an underscore in the label, I am fairly
> >> sure it was al
Nick,
>> On Wed, 02 Nov 2011 09:38:20 -0400, Nick Dokos said:
> Myles English wrote:
>>
>> There is (git from a couple of days ago) a problem with referring
>> to equations containing an underscore in the label, I am fairly
>> sure it was allowed before, e.g.:
>>
>> #+LABEL: Equ
Andrew Hyatt writes:
Hi, Andrew,
> Would anyone be interested in the ability to archive to the current
> date in date-tree instead of an archive file? I'm toying with the
> idea of implementing this, and I could send it in as a patch when it
> is done,
I agree with suvayu.
> or just leave it a
Bastien writes:
> Hi Christian,
>
> Christian Moe writes:
>
>> I've signed the FSF papers (assignment 711933).
>
> Great.
+1
>
>> Bastien, shall I just add myself to the list, or is there more
>> procedure?
>
> I added you to the relevant Worg page:
> http://orgmode.org/worg/org-contribute.htm
On Wed, 2 Nov 2011 10:02:06 -0400
Andrew Hyatt wrote:
> Would anyone be interested in the ability to archive to the current
> date in date-tree instead of an archive file? I'm toying with the
> idea of implementing this, and I could send it in as a patch when it
> is done, or just leave it as a
On Wed, Nov 2, 2011 at 1:57 PM, Brian Wightman
wrote:
> On Tue, Nov 1, 2011 at 10:17 AM, Eric Schulte
> wrote:
> > This is also after all the development repository, and while I do try
> > very hard never to break this head of this repository at the same time I
> > think it is an acceptable place
On Wed, Nov 2, 2011 at 15:02, Andrew Hyatt wrote:
> Would anyone be interested in the ability to archive to the current
> date in date-tree instead of an archive file? I'm toying with the
> idea of implementing this, and I could send it in as a patch when it
> is done, or just leave it as a perso
On Wed, Nov 2, 2011 at 1:18 PM, Nicolas Goaziou wrote:
> Hello,
>
> Rainer M Krug writes:
>
> > Then one should possibly also think of merging #+LATEX into #+PROPERTY -
> > which I think would make it more consistent (and this is a serious
> > suggestion).
>
> Are you sure you're talking about t
Would anyone be interested in the ability to archive to the current
date in date-tree instead of an archive file? I'm toying with the
idea of implementing this, and I could send it in as a patch when it
is done, or just leave it as a personal module if no one is
particularly interested.
Myles English wrote:
>
> There is (git from a couple of days ago) a problem with referring to
> equations containing an underscore in the label, I am fairly sure it was
> allowed before, e.g.:
>
> #+LABEL: Equation:new_eq
> \begin{equation}
> x=\sqrt{b}
> \end{equation}
>
> Refe
On 02/11/11 13:13, Nick Dokos wrote:
Ian Barton wrote:
If I have a large begin_src block it can make reading the surrounding
text difficult, as the reader has to keep paging up and down. Ideally
it would be possible to fold src blocks, but I can see that would be
inconsistent with org's struct
Jambunathan,
>> On Wed, 02 Nov 2011 01:09:41 +0530, Jambunathan K said:
> Myles
> (I have read the followup post to this set of questions)
> Myles English writes:
On Mon, 31 Oct 2011 03:41:18 +0530, Jambunathan K said:
>>
>> > Myles English writes: >> I have found
>> that
Ian Barton wrote:
> If I have a large begin_src block it can make reading the surrounding
> text difficult, as the reader has to keep paging up and down. Ideally
> it would be possible to fold src blocks, but I can see that would be
> inconsistent with org's structure. I could put the block in a
On Tue, Nov 1, 2011 at 10:17 AM, Eric Schulte wrote:
> This is also after all the development repository, and while I do try
> very hard never to break this head of this repository at the same time I
> think it is an acceptable place to try out new functionality.
Given that a common recommendatio
On Nov 2, 2011, at 11:10 AM, Bastien wrote:
> Hi Carsten,
>
> Carsten Dominik writes:
>
>> please find enclosed a patch which is my proposal for rounding
>> off this feature.
>
> thanks for the clean implementation.
>
> There is a small typo: the second (let ...) should be (let* ...),
> see
Hello,
Rainer M Krug writes:
> Then one should possibly also think of merging #+LATEX into #+PROPERTY -
> which I think would make it more consistent (and this is a serious
> suggestion).
Are you sure you're talking about the "#+LATEX:" keywords, allowing to
insert LaTeX code only for the LaTeX
Hi Suvayu,
suvayu ali writes:
> However I did find a solution along those lines and the final patch is
> attached. :)
Great. I've applied this patch now, thanks for your work on this!
Best,
--
Bastien
Hi Carsten,
Carsten Dominik writes:
> please find enclosed a patch which is my proposal for rounding
> off this feature.
thanks for the clean implementation.
There is a small typo: the second (let ...) should be (let* ...),
see attached updated patch.
> It introduces a variable, applies the c
Hi Christian,
Christian Moe writes:
> I've signed the FSF papers (assignment 711933).
Great.
> Bastien, shall I just add myself to the list, or is there more
> procedure?
I added you to the relevant Worg page:
http://orgmode.org/worg/org-contribute.html#contributors_with_fsf_papers
Thanks!
Hello,
Bernt Hansen writes:
> This patch works too
I've pushed it to master. Thanks again for reporting the problem and
testing the patches.
Regards,
--
Nicolas Goaziou
On Tue, Nov 1, 2011 at 4:17 PM, Eric Schulte wrote:
> Nick Dokos writes:
>
> > Nick Dokos wrote:
> >
> >
> >> Can we please back off this path?
> >
> > In order to prevent confusion or needless argument: the path I think we
> > should back off of is the committing of these changes to master - I
On Wed, Nov 2, 2011 at 03:43, suvayu ali wrote:
> You could try replacing that with the following:
>
> pdflatex -interaction nonstopmode -output-directory %o
> \pdfminorversion=4 $(cat %f)
I did some testing. The following should work.
pdflatex -interaction nonstopmode -output-directory %o
\\pdf
Hi,
I've signed the FSF papers (assignment 711933).
Bastien, shall I just add myself to the list, or is there more procedure?
Yours,
Christian Moe
If I have a large begin_src block it can make reading the surrounding
text difficult, as the reader has to keep paging up and down. Ideally it
would be possible to fold src blocks, but I can see that would be
inconsistent with org's structure. I could put the block in a draw, but
was interested
Hi Bastien,
please find enclosed a patch which is my proposal for rounding
off this feature.
It introduces a variable, applies the check to org-delete-char
and org-delete-backward-char, and removes the (sit-for 1),
and it never moves the cursor.
I have been unsing it for a day or two, and I lik
55 matches
Mail list logo
