I needed to enter information for two dates in org-mode and went into
calendar using c-c+! and got the current date as expected then hit c-b to
move the date to yesterday and pointer remained on today's date. So I
ended up hitting on today's date and editing it in the actual org
file and fill
Herbert Sitz writes:
> Last week I finally got around to testing the export to ODT that Jambunathan's
> made available. Here's a 3 minute video showing how it works (calling odt
> export from a document open in VimOrganizer):
> http://vimeo.com/31564708
>
> This is some seriously cool functional
Herbert Sitz writes:
> Here's a 3 minute video showing how it works (calling odt export from
> a document open in VimOrganizer): http://vimeo.com/31564708
Thanks, it is a nice video. You should add it to the Worg.
> This is some seriously cool functionality for Org that deserves wider
> exposur
Michael Brand gmail.com> writes:
>
> or at a similar place that there is also the possibility to have the
> vi modal editing paradigm and most of the vi key bindings within Emacs
> itself by using a vi emulation like Viper mode. (I use Emacs with
> Viper mode all the time to have the best of both
Hi Nikolai,
> As I can hardly be the only person with two computers, a mobile, and a
> desire to keep my org-agenda-files in sync between these three
> computers, I’ll pose this question here: How do you have this set up?
I am using git to sync several laptops and Desktop computers.
Every 5 minu
Hi Herb
On Thu, Nov 3, 2011 at 01:31, Herbert Sitz wrote:
> I'd be glad to hear any feedback, comments, suggestions. . .
My intention is the opposite of undermining your work in any way and I
find it a good thing that users who prefer Vim can handle Org files
too. But for completeness and becaus
Hi, all,
On the last few days I've been working on a major mode derived from org-mode.
While I was at it, I've encoutered some difficulties related to those reported
by the OP (Stefan). Specifically: in a lot of places, org-mode will check if
it's the current major-mode and, if it's not, will refu
Hello,
Before enhancing org-agenda-to-appt (and some other parts) to fit my
needs, I would like to get some feedback for my ideas:
- General opinions about the ideas.
- Hints about already existing usable code.
- Hints how to implement the ideas with the least effort.
The general idea is, to get
Hi Nicolas
On Thu, Nov 3, 2011 at 21:43, Nicolas Goaziou wrote:
> I have pushed a fix in master. Thanks for reporting this.
Resolved, thanks.
Michael
Hello,
Michael Brand writes:
> Git bisect finds it as the reason of a fontification issue of
> headings with the keyword COMMENT or QUOTE:
> - the face falls back from org-special-keyword to org-level-
> - hidestars does not hide any more
>
> #+begin_src org
> ,#+STARTUP: odd showall hidestars
Nicolas Goaziou writes:
> Eric Schulte writes:
>
On the contrary, creating a block for each keyword would mean a lot of
new syntax.
We currently have 8 types of blocks (not counting dynamic blocks, whose
syntax is a bit different), all requiring to be parsed differently:
One more idea that has occurred to me, it should give all of the
functionality which we desire (i.e., the ability for a property value to
span multiple lines and to be accumulated at the subtree level), and it
should require *no* new syntax. The only problem is it puts a
limitation on possible pro
On 11/3/11 8:57 PM, Herbert Sitz wrote:
This is some seriously cool functionality for Org that deserves wider exposure.
Jambunathan's done a great job.
+1
Christian
Eric Schulte writes:
>>> On the contrary, creating a block for each keyword would mean a lot of
>>> new syntax.
>>>
>>> We currently have 8 types of blocks (not counting dynamic blocks, whose
>>> syntax is a bit different), all requiring to be parsed differently:
>>>
>>> 1. Center blocks,
>>>
Last week I finally got around to testing the export to ODT that Jambunathan's
made available. Here's a 3 minute video showing how it works (calling odt
export from a document open in VimOrganizer):
http://vimeo.com/31564708
This is some seriously cool functionality for Org that deserves wider ex
While I still think `org-accumulated-properties-alist' is the most
powerful solution -- as it is the only solution which allows a subtree
property block to extend rather than overwrite a file-wide property.
I've been thinking a little bit more about these issues and I'm
returning to a previous sugg
Hi!
I would like to use Org mode with MobileOrg over Dropbox and have all
my org-agenda-files synced between all my computers, that is, my home
computer, my work computer, and my mobile. Currently, as I understand
MobileOrg and org-mobile-push/-pull, MobileOrg is only really designed
to sync betw
Rainer - if he feels uncomfortable - can choose *not* to update his git
repo and switch his local checkout to a historical version.
> [1] to see the info page evaluate (info "(elisp)File Local
> Variables")
A usage note for adding these variables without straining the brain.
M-x add-file-local
Perhaps this thread should be merged with the
About commit named "Allow multi-line properties to be specified in property
blocks"
thread?
Best -- Eric
Robert McIntyre writes:
> In my literate org projects at http://aurellem.com/, I often have to
> use very long lines such as:
>
> #+descrip
Jambunathan K wrote:
>
> > Not sure I follow completely, but I will continue trying to cajole others
> > to provide the actual patches and limit myself to providing guidance if
> > necessary.
>
> Thanks for *not* submitting a patch.
>
> What I meant was - there is a process in place and Emacs
>> >
>> > 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 think the work should be done in a branch and cooked
>> >thoroughly before merging it to master.
>> >
>>
>
> Partly agree here - I was bitten
> Not sure I follow completely, but I will continue trying to cajole others
> to provide the actual patches and limit myself to providing guidance if
> necessary.
Thanks for *not* submitting a patch.
What I meant was - there is a process in place and Emacs project + FSF
are quite earnest as far
>
> But allowing a top-level :PROPERTIES: drawer with properties
> whose scope is the entire file looks like a good idea to me.
>
I don't see what this would add, how would this solve the need for
multi-line properties, and how would it differ from IMO being uglier
than a series of #+PROPERTY: lin
I don't understand why the `org-accumulated-properties-alist' solution
seems like a hack, could someone elaborate. To me that still feels like
the most natural solution.
more below...
>>> 2) "Cumulative properties"?
>>>
>>>Here is a suggestion: use a syntaxe like
>>>
>>>#+var: foo 1
>>
Myles English writes:
>>> On Wed, 02 Nov 2011 21:38:42 +, Myles English said:
>
>>> 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
Jambunathan K wrote:
>
> > Oh, I thought I had run out on my quota: I do have a patch that I can
> > send in, I just don't want to cause headaches (particularly to you)
> > down the line. I'll add a Changelog, mark it as a TINYCHANGE and send it in
> > -
> > is that OK?
>
> AFAIK, there is fai
On Thu, Nov 3, 2011 at 12:55 PM, suvayu ali wrote:
> On Thu, Nov 3, 2011 at 18:48, John Hendy wrote:
>> On Wed, Nov 2, 2011 at 5:30 AM, suvayu ali
>> wrote:
>>> On Wed, Nov 2, 2011 at 03:43, suvayu ali
>>> wrote:
You could try replacing that with the following:
pdflatex -intera
Hi Nicolas
Thanks for applying
commit dfcb6faef11a2439b56b18a6289803361d402130
Author: Nicolas Goaziou
Date: Thu Aug 25 01:58:29 2011 +0200
Provide more consistent regexps for headlines
Git bisect finds it as the reason of a fontification issue of
headings with the keyword COMMENT or QUO
Thank you for sharing your experiences guys,
I only started thinking about this recently, when I had to send some
documents to a banker. The issue is that I'm sure most bankers are not
internet-savvy, they might not even know how to download something from a
website (the alternative would be to pu
On Thu, Nov 3, 2011 at 18:48, John Hendy wrote:
> On Wed, Nov 2, 2011 at 5:30 AM, suvayu ali
> wrote:
>> 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 $(c
On Wed, Nov 2, 2011 at 5:30 AM, suvayu ali wrote:
> 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.
>
Hi Carsten
On Thu, Oct 13, 2011 at 10:27, Carsten Dominik
wrote:
> I am attaching a patch which will make time stamps without a day name
> like <2011-10-12> work correctly. Furthermore, pressing C-c C-c on
> a time stamp will fill in or fix the day name.
>
> However, I am not sure if this patch
> Oh, I thought I had run out on my quota: I do have a patch that I can
> send in, I just don't want to cause headaches (particularly to you)
> down the line. I'll add a Changelog, mark it as a TINYCHANGE and send it in -
> is that OK?
AFAIK, there is fair amount of audit of ChangeLogs that is do
Hi,
I am trying to export a simple project plan from org to taskjuggler
through org-taskjuggler.el. I cannot get the behavour I expect and
need do some manual tweaks to get the taskjuggler file working. The
questions are as follows, whereafter the test org-file that I attempt
export and finally th
Christian Moe wrote:
> On 11/3/11 2:26 AM, Bastien wrote:
> > Hi Nicolas,
> >
> > Nicolas Goaziou writes:
> (...)
> >> There is also "#+bind:", whose purpose is close enough.
> >
> > Indeed. Eric, would it be possible to use
> >
> > #+bind foo 1
> >
> > instead of
> >
> > #+property var foo=1
>
>> On Wed, 02 Nov 2011 21:38:42 +, Myles English said:
>> 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 f
Bastien wrote:
> 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 leg
> Sorry, I didn't get into too much detail here because I had the
> feeling that the problem might have been cause by me not being able
> to use the package manager correctly rather than the package manager
> itself. But if it could help others, of course, I'm sharing the
> details as far as I und
Am 03.11.2011 um 12:03 schrieb Jambunathan K:
>> It says "Org-mode version 7.7". However, I feel that there was
>> something strange with my installation. I checked my files in my Emacs
>> folder and everything seemed really messed up, so I just reinstalled
>> org from the latest build and now it
There is another issue with export (to HTML) that I found out only now
to be related with indentation: The example below exports like
expected but when all lines below project are indented (by two spaces)
then the lines BEGIN and END are also exported.
* project
#+BEGIN: columnview :maxlevel 3 :id
> It says "Org-mode version 7.7". However, I feel that there was
> something strange with my installation. I checked my files in my Emacs
> folder and everything seemed really messed up, so I just reinstalled
> org from the latest build and now it works! I had tried that before
> automatically with
Hi
Sorry - I mentioned it already, but I have lost track of how things are
standing at the moment.
I am using Org-mode version 7.7 (release_7.7.512.g4d2a), and get, based on
the following arguments, after tangling, a file which begins with:
##
[[file:~/Documents/Projects/BiocontrolAndAlienDynam
Am 03.11.2011 um 01:36 schrieb Nick Dokos:
> 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-e
On 11/3/11 2:42 AM, Bastien wrote:
But allowing a top-level :PROPERTIES: drawer with properties
whose scope is the entire file looks like a good idea to me.
How other would feel about this?
Not sure if this is already clear, but just in case: The functionality
is already there. PROPERTY lin
Thorsten writes:
sorry, incomplete sentence, wrong keystroke ...
> nice, I announced this on the picolisp newsgroup, since this new
> org-babel language is more vim based, and VimOrganizer might help to
...spread the news about orgmode and org-babel in the
picolisp community.
cheers
--
Thor
Herbert Sitz writes:
> I just formally pushed up a new version of VimOrganizer, an Org clone in Vim.
nice, I announced this on the picolisp newsgroup, since this new
org-babel language is more vim based, and VimOrganizer might help to
--
Thorsten
On 11/3/11 2:26 AM, Bastien wrote:
Hi Nicolas,
Nicolas Goaziou writes:
(...)
There is also "#+bind:", whose purpose is close enough.
Indeed. Eric, would it be possible to use
#+bind foo 1
instead of
#+property var foo=1
Correct me if I'm wrong, but the purpose of #+BIND is to specify
Hmmm...
nice! Maybe it helps to bring finally peace between Vi and Emacs users. I
will forward it to my Vi-friends:)
Torsten
On Nov 3, 2011 9:31 AM, "Herbert Sitz" wrote:
> I just formally pushed up a new version of VimOrganizer, an Org clone in
> Vim.
>
> This version is much closer to being a t
48 matches
Mail list logo
