-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/04/12 19:30, Eric Schulte wrote:
> Hi Karl,
>
> I think the Org-mode manual is also citable.
Never thought about that - good to know.
Why not put that into org? e.g. R has a function citation(), which returns the
bibtex for citing R
or packag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/12 23:51, Eric Schulte wrote:
> Torsten Wagner writes:
>
>> Hi,
>>
>> for me the biggest "trouble" with babel is to remember the possible keywords
>> in the header
>> for different languages. There were a lot of ongoing syntax change which
On Tue, Apr 10, 2012 at 09:55, Rainer M Krug wrote:
> Why not put that into org? e.g. R has a function citation(), which returns
> the bibtex for citing R
> or packages.
Nice idea, why not submit a patch? ;)
--
Suvayu
Open source is the future. It sets us free.
* Bastien wrote:
> Bastien writes:
>
>>> Is there any other important paper I missed?
>>
>> Check: http://orgmode.org/fr/org-mode-documentation.html
>
> English: http://orgmode.org/org-mode-documentation.html
> Spanish: http://orgmode.org/es/org-mode-documentation.html
> Japanese: http://orgmode.
Karl Voit writes:
> * Bastien wrote:
>> Bastien writes:
>>
Is there any other important paper I missed?
>>>
>>> Check: http://orgmode.org/fr/org-mode-documentation.html
>>
>> English: http://orgmode.org/org-mode-documentation.html
>> Spanish: http://orgmode.org/es/org-mode-documentation.ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/12 10:57, suvayu ali wrote:
> On Tue, Apr 10, 2012 at 09:55, Rainer M Krug wrote:
>> Why not put that into org? e.g. R has a function citation(), which returns
>> the bibtex for
>> citing R or packages.
>
> Nice idea, why not submit a patch
Hi Rainer,
Rainer M Krug writes:
> On 10/04/12 10:57, suvayu ali wrote:
>> On Tue, Apr 10, 2012 at 09:55, Rainer M Krug wrote:
>>> Why not put that into org? e.g. R has a function citation(), which returns
>>> the bibtex for
>>> citing R or packages.
>>
>> Nice idea, why not submit a patch? ;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/12 11:13, Bastien wrote:
> Hi Rainer,
>
> Rainer M Krug writes:
>
>> On 10/04/12 10:57, suvayu ali wrote:
>>> On Tue, Apr 10, 2012 at 09:55, Rainer M Krug wrote:
Why not put that into org? e.g. R has a function citation(), which retur
* Karl Voit wrote:
>
> http://orgmode.org/worg/org-papers.html
>
> I'd love to link bib-files with every entry. Where should I put them
> on Worg?
>
> Some paths I can think of:
>
> code/bibtex/*
> org-contrib/bibtex/*
I placed it in «org-contrib/bibtex/».
Unfortunately I can not
Hi,
I started to use lisp (as well as other) code blocks more and more to
modify my work environment (emacs) for a particular (buffer-based)
task.
That is I change some variables, add some stuff etc.
A real world example is for example the section below
* Set-up
Hi Karl,
Karl Voit writes:
> * Karl Voit wrote:
>>
>> http://orgmode.org/worg/org-papers.html
>>
>> I'd love to link bib-files with every entry. Where should I put them
>> on Worg?
>>
>> Some paths I can think of:
>>
>> code/bibtex/*
>> org-contrib/bibtex/*
>
> I placed it in «o
Bastien writes:
[snip]
> See this footnote in the section "8.3.1 Inserting deadlines or
> schedules" of the manual:
>
>(1) The `SCHEDULED' and `DEADLINE' dates are inserted on the line
> right below the headline. Don't put any text between this line and the
> headline.
Hi. Then I guess the e
Hi Jérémie,
jca+...@wxcvbn.org (Jérémie Courrèges-Anglas) writes:
> Bastien writes:
> [snip]
>> See this footnote in the section "8.3.1 Inserting deadlines or
>> schedules" of the manual:
>>
>>(1) The `SCHEDULED' and `DEADLINE' dates are inserted on the line
>> right below the headline. Don
>> On Sun, 01 Apr 2012 12:38:12 -0400, Eric Schulte
>> wrote:
>>
> I'm not clear on how this differs from the messages produced using
> org-mime-htmlize, and it has been a while since I've looked into email
> mime mechanics. However, since the emails generated using
> org-mime-h
Dear all,
I am not sure if this an orgmode-, an ESS- or an Emacs-related question.
I am working on an orgmode-file with embedded R code. Since I am using a
build tool called waf, I would like to call Emacs from command line like
this:
emacs --batch --load "e:/config/.emacs" --visit test.org --fu
Bastien writes:
[snip]
> I added "TINYCHANGE" in the commit message. Please do so for small
> changes when you are not a FSF-signed contributor.
Oops, forgot that, thanks for the reminder, and thanks to the Org-mode
developers and community for such a great piece of software.
--
Jérémie Courrè
jca+...@wxcvbn.org (Jérémie Courrèges-Anglas) writes:
> Bastien writes:
> [snip]
>> I added "TINYCHANGE" in the commit message. Please do so for small
>> changes when you are not a FSF-signed contributor.
>
> Oops, forgot that, thanks for the reminder, and thanks to the Org-mode
> developers and
Am 09.04.2012 16:51, schrieb Bastien:
> Hi Dave,
>
> Dave Abrahams writes:
>
>> Sorry, but I don't want to spend the time on that. I'm trying to get
>> the rules changed so that it isn't so easy to corrupt an org file.
>
> The current rule is "Leave SCHEDULED: and DEADLINE: information where
Hi Rainer,
Rainer Stengele writes:
> why does the function fire in this case:
>
> * test
> ** TODO task
>SCHEDULED: <2012-04-10 Di>
Because it was buggy -- here is a better version (also updated on Worg)
(defun org-check-misformatted-subtree ()
"Check misformatted entries in
Hi!
I do have a simple yasnippet template:
,[ ~/.emacs/yasnippets/text-mode/org-mode/test ]
| # name : test snippet
| # # --
| ** $1 $2 :$1$2:
| $0
`
When I invoke the snippet using »test« followed by the TAB key,
yasnippet correctly inserts the template. But after pressing the
first ke
Hello Bastien
Thanks for the fix and it addresses the problem I reported. Feel free
to close this bug once you commit the changes to bzr repo.
Jambunathan K.
Hi Mike,
I just reverted the commits I pushed for fixing this "issue".
Mike McLean writes:
> The expected result is a completion list of tag_a and tag_b, this
> does not work and the Minibuffer prompts [No match]
I cannot do any better than to quote Matt Lundin on this:
"Historically, only ta
Hi Bernt,
Bernt Hansen writes:
> This error is gone but I see other problems.
>
> When completing tags with C-c C-q TAB and selecting a tag that is part
> of a group which are supposed to be mutually exclusive it doesn't
> remove other existing tags in that group.
This error was introduced by t
Hi Simon,
Simon Thum writes:
> I have found some irritating behaviour, potentially a bug. I have a block
> agenda which goes like:
>
> tags-todo "@home&TODO=\"TODO\"
>
> and it displays a certain org line that reads
>
> TODO_ state triggers
Can you try the following patch (against latest h
Hi Carsten and all,
Carsten Dominik writes:
> since we did make a change to Org a while ago to allow date stamps
> without the name of the day, I think it is only consequent to also do
> it for this case. Must have slipped our attention back then.
> The only thing we must ensure is that this re
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
> I added "Du " as a prefix to get going, but the ideal would be to
> directly use 2012-02-29 as the link description. Is there a way, or is
> it a limitation (or a bug)?
I would call it a limitation.
--
Bastien
Bastien wrote:
> Hi Carsten and all,
>
> Carsten Dominik writes:
>
> > since we did make a change to Org a while ago to allow date stamps
> > without the name of the day, I think it is only consequent to also do
> > it for this case. Must have slipped our attention back then.
> > The only thi
Hi Eric and all,
Eric Schulte writes:
> On March 25th in Albuquerque New Mexico at the monthly meeting of the
> Albuquerque Lisp/Scheme user group.
Please don't hesitate to store informations about Org Workshops on
Worg! That will help other workshops to happen, and to reuse existing
content.
Nick Dokos writes:
> I think he did already (but please check!):
>
> commit 7d84b300f4cba8b726662113d4ce4ff40a76c5b5
You're right -- time to power off my computer :)
Thanks!
--
Bastien
Torsten Wagner writes:
> Hi,
> I started to use lisp (as well as other) code blocks more and more to
> modify my work environment (emacs) for a particular (buffer-based)
> task.
> That is I change some variables, add some stuff etc.
> A real world example is for example the section below
>
> * Se
Interesting
The very first report I submitted (
http://comments.gmane.org/gmane.emacs.orgmode/53824 ) showed the historic
behavior correct (the two tags defined in org-tag-alist show up in the fast
tag completion window). The "bug" was after shifting to free tag selection
mode, the tags defined in
On Tuesday, March 27, 2012, Bastien wrote:
>
> > Shouldn't free tag entry always show all possible tags, regardless of
> > the setting of or use of fast tag completion?
>
> I think so -- thanks a lot for the detailed report.
Yes, this is the crux of the problem as first reported. Note that the f
Bastien writes:
> Hi François,
Bonjour, Bastien!
>> I added "Du " as a prefix to get going, but the ideal would be to
>> directly use 2012-02-29 as the link description. Is there a way, or is
>> it a limitation (or a bug)?
> I would call it a limitation.
Could it be documented somewhere appr
Hi,
at the changes page of the orgmode website, some of the code block
formatting seems to be broken (see http://orgmode.org/Changes.html#sec-3).
Can anyone please check if the attached patch would fix this? With my
local setup, this yields a proper display of the code blocks. Or do the
co
Hi Rainer,
Rainer M Krug writes:
> It just returns the citation.
Okay. I've added this to the Worg FAQ:
* Is there a bibtex entry for the Org manual?
Yes. Please evaluate this function and run =M-x
org-insert-manual-bitex-citation-at-point RET=.
#+begin_src emacs-lisp
(defun org-insert-man
Guys,
let me know when you have a first stable draft for the structure of the
Babel menu and I'll implement it.
Thanks,
--
Bastien
Hi John,
John Wiegley writes:
> I discovered the < key in the agenda yesterday (by accident!), which filters
> the Agenda down to entries having the same category.
>
> However, I use both *categories* and *projects*. For example:
>
> * Work
> :CATEGORY: Work
> :OVERLAY: (face (:backg
Bonjour François,
pin...@iro.umontreal.ca (François Pinard) writes:
> Bastien writes:
>
>> Hi François,
>
> Bonjour, Bastien!
>
>>> I added "Du " as a prefix to get going, but the ideal would be to
>>> directly use 2012-02-29 as the link description. Is there a way, or is
>>> it a limitation (o
Funkload is an HTTP functional test and load tool. In the FAQ, there is
this:
,
| How to modify a report ?
|
| The report is in reStructuredText, the index.rst can be edited in text
| mode, to rebuild the html version:
|
| rst2html --stylesheet=funkload.css index.rst --traceback > index.
Samuel Wales writes:
> Long shot: is making worg more wiki-like practical?
Worg = Ikiwiki + Org?
http://lists.gnu.org/archive/html/emacs-orgmode/2011-12/msg00431.html
It wouldn't be a bad idea to ask Ikiwiki folks to support Org-mode
natively. I dropped a note to them a few weeks ago, btw.
--
Nick Dokos writes:
> See http://funkload.nuxeo.org/faq.html#how-to-modify-a-report
Yeah. That's great! Thanks for sharing this.
--
Bastien
Hi Sébastien,
"Sebastien Vauban" writes:
> Using the flag T does not help:
>
> | Planning | 00:00:03 |
> | Reporting | 00:00:09 |
> #+TBLFM: @1$2=remote(hours-spent,@4$4);T
This should work as expected now (with the "T" flag.)
Note that the conversion of 3:12 into 1:4 is independant
of getti
Please do a
~$ cd [your-org-clone-dir/]
~$ git fetch --tags origin
as I updated the release_7.8.08 tag by annotating it.
Thanks,
--
Bastien
Hi Sébastien,
"Sebastien Vauban" writes:
> This can be best understood with an example...
I've been thinking about this again and I made up my mind with a clearer
argument.
> Before:
>
> #+BEGIN: clocktable :maxlevel 4 :scope ("file-abc-tom.org"
> "file-abc-ann.org") :block 2012-02
>
Hi Christian,
Thanks for your reply.
I left implicit the question of whether this can solve OP's problem
also, but believe it is potentially related.
However, if I understood CSS well enough to ask the question
precisely, I'd have the answer. So bear with me.
More below:
On 2012-04-07, Christ
Nicolas Goaziou writes:
> Just use two different drawer names, and select which one to actually
> export through i.e. #+OPTIONS: d:("EN"). No need for extra syntax.
Well, the manual says, in node Export options:
d: turn on/off inclusion of drawers
So one would never guess from the
Memnon Anon writes:
> pin...@iro.umontreal.ca (François Pinard) writes:
>> I often cut a list item (or a hierarchy of list items) to reinsert it
>> into another heading which I know contains only list items. All the
>> headings are collapsed, so what I usually do is position the cursor at
>> th
pin...@iro.umontreal.ca (François Pinard) writes:
> [...] so what I usually do is position the cursor at
> the beginning of the /next/ heading and yank the list item there. [...]
> However, by mistake, it happens that the cursor is on the only visible
> bullet star of the next heading (I'm using
Hi guys,
I know there are quite a few smart brains around here, and I think this is
valid discussion for this mailing list, even if OT.
I'm not a cientist, nor work inside an academic environment. I'm just a
regular guy trying to understand this world and making better use of my
resources, specia
Hi there,
Does anybody has a script that convert latex files to org mode ?
I wrote one in Matlab, but it is a little clunky - I wrote it in matlab
because I am still learning lisp
thanks
M
Marvin Doyley writes:
> Does anybody has a script that convert latex files to org mode ?
>
> I wrote one in Matlab, but it is a little clunky - I wrote it in matlab
> because I am still learning lisp
Not exactly a script, but I highly recommend Pandoc[1]. There is also
pandoc-mode[2], which is a
t...@tsdye.com (Thomas S. Dye) writes:
> Eric Schulte writes:
>
>> Torsten Wagner writes:
>>
>>> Hi,
>>>
>>> for me the biggest "trouble" with babel is to remember the possible
>>> keywords in the header for different languages.
>>> There were a lot of ongoing syntax change which did not make it
Rainer M Krug writes:
> Hi
>
> There are regularly questions concerning file wide properties set with
>
> #+PROPERTY:
>
> which are simply caused by not C-c C-c before tangling / executing block.
>
> Would it be an option to apply these headers automatically e.g. in the
> pre-tangling hook
Applied, thanks!
Dov Grobgeld writes:
> Sure. They should be equivalent. (In C++ return is prefered as it calls
> destructors. But anyone relying on this when using C++ in org-mode should
> imnsho get a permanent ban from ever using C/C++ ;-).
>
> Regards,
> Dov
>
> On Thu, Apr 5, 2012 at 17:56,
François Pinard wrote:
> Nicolas Goaziou writes:
>
> > Just use two different drawer names, and select which one to actually
> > export through i.e. #+OPTIONS: d:("EN"). No need for extra syntax.
>
> Well, the manual says, in node Export options:
>
> d: turn on/off inclusion of d
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
> Nicolas Goaziou writes:
>
>> Just use two different drawer names, and select which one to actually
>> export through i.e. #+OPTIONS: d:("EN"). No need for extra syntax.
>
> Well, the manual says, in node Export options:
>
> d:
On Wed, Apr 11, 2012 at 03:10:33AM +0530, Jambunathan K wrote:
> Samuel Wales writes:
>
> > Long shot: is making worg more wiki-like practical?
>
> Worg = Ikiwiki + Org?
>
> http://lists.gnu.org/archive/html/emacs-orgmode/2011-12/msg00431.html
>
> It wouldn't be a bad idea to ask Ikiwiki folks to
Uwe Brauer writes:
>>> On Sun, 01 Apr 2012 12:38:12 -0400, Eric Schulte
>>> wrote:
>>>
>
>> I'm not clear on how this differs from the messages produced using
>> org-mime-htmlize, and it has been a while since I've looked into email
>> mime mechanics. However, since the emails
Hi Nicholas,
(btw, do you prefer "Nick" or "Nicholas"?)
Nick Dokos writes:
> None of this is an argument for leaving the manual as is: if you had a
> problem finding the information, then others will too, so the manual
> should be improved.
Done.
> But the information is there, and moreover,
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
> pin...@iro.umontreal.ca (François Pinard) writes:
>
>> [...] so what I usually do is position the cursor at
>> the beginning of the /next/ heading and yank the list item there. [...]
>> However, by mistake, it happens that the cur
Hi Thorsten,
Thorsten writes:
> Memnon Anon writes:
>
>> pin...@iro.umontreal.ca (François Pinard) writes:
>
>>> However, by mistake, it happens that the cursor is on the only visible
>>> bullet star of the next heading instead of really being at the start
>>> of the line.
>
> I recently edit
Ivy Foster writes:
> On 09 Mar 2012, at 3:09 am +0100, Bastien wrote:
>> Mathias Bauer writes:
>> > As default, all level 1 headlines are underlined by -
>> > characters and level 2 headlines with =. Wouldn't it be
>> > more logical the other way round
>
>> Unless many users think this is illog
62 matches
Mail list logo
