On 2014-10-25 11:00, "Charles C. Berry" writes:
> OK, thanks. It had to be something in my init.
>
> I have (defun org-mode-reftex-setup () ... ) from
>
> http://www.mfasold.net/blog/2009/02/using-emacs-org-mode-to-draft-papers/
>
> in my init.
Interesting, I have this
#+begin_src emacs-lisp
;;
Thank you.
I wonder if it is worth including this usage in the manual?
---
Hi Thierry,
abonnements writes:
Hi,
I would like to know if it is possible to desactivate a previously
"open session".
Example :
* Test
:PROPERTIES:
:HEAGER-ARGS: :session SESS
I had the following snippets in my .emacs which allowed me to call up a
mini-emacsclient frame to quickly add notes and TODOs etc. It doesn't
seem to work anymore (it comes up, but as soon as I choose [t], [n]
etc. it disappears). Is there an updated recommendation on how to do
this?
###
You could hide the state changes if you put (setq org-log-into-drawer
"LOGBOOK") in your init file. I don't know how to hide the CLOSED tag
though.
On Sun, Oct 26, 2014 at 11:32 AM, Maciej Kalisiak
wrote:
> When I do C-c t d (TODO -> DONE) or similar status change on a TODO item,
> it accumulate
I think it would be helpful if on the weekly agenda view there were a way
to hide a task for one day only. For example, if there were a task that I
knew I wouldn't get to today, I could hit 'm', the status would stay as
TODO, but it wouldn't show up under this particular agenda view.
The only semi
Hi Nathaniel
On Sun, Oct 26, 2014 at 2:27 AM, Nathaniel Flath wrote:
> I'm fine with adding the (when all log-first-time). I don't want to leave
> it unconditional
Ok, then I agree on (when all log-first-time).
Michael
Per Unneberg writes:
> Hi,
>
> I'm writing a custom function for use with a capture template, as
> described in the section Template elements (sec 9.1.3.1) of the info
> manual. My function does what I expect in that it finds the correct
> heading (in my use case "Log") and returns point. However
Pete Ley writes:
>> All I've got now are a function that finds the logbook, and another that
>> parses the log items and normalizes them: extracts the TODO
>> states/timestamps/key-values and sets them as properties on the items
>> themselves. Then you've got a pretty good basis from which to do
When I do C-c t d (TODO -> DONE) or similar status change on a TODO item,
it accumulates meta-data like:
CLOSED: [2014-10-26 Sun 11:25]
- State "DONE" from "TODO" [2014-10-26 Sun 11:25]
So each such item "blows up" on screen from 1 line to 3 lines.
I do want to collect this data, b
Nicolas Goaziou writes:
> As discussed previously, I would like to modify property drawers syntax.
> The change is simple: they must be located right after a headline and
> its planning line, if any.
[...]
> I pushed a new branch, "top-properties" in the repository for code
> review and testing
Rasmus writes:
>> I also note that these tocs do not have any title. Would it make sense
>> to remove title from local tocs in other back-ends too?
>
> No idea. Both makes sense, but maybe including the TOC-title is too
> verbose? In any case, I think it's easy to add a title if you. Based
> o
Hi,
I have recently started using org mode. And I am trying out capture mode. I
have two org files one for tasks and another for notes. I keep all the
todos in tasks.org and notes in notes.org. So whenever, I need to record
some notes related a todo item in tasks.org I use capture mode and enter
n
Nicolas Goaziou writes:
> Rasmus writes:
>
>> It happened to me now when I was editing a table and clicked TAB.
>>
>> Debugger entered--beginning evaluation of function call form:
>> * (byte-code "\301\302\303!\207" [quit-flag t eval (ignore nil)] 2)
>> flyspell-post-command-hook()
>> recurs
Hi,
Nicolas Goaziou writes:
> Rasmus writes:
>
>> I think we can do it with titletoc. I have used other functionality
>> of titletoc, and it 'doesn't sucks'ᵀᴹ. Below is an example. The
>> output is more inline with normal tocs, but you can also style it
>> [I've used this for making paragrap
Hi Thierry,
abonnements writes:
> Hi,
> I would like to know if it is possible to desactivate a previously
> "open session".
> Example :
> * Test
> :PROPERTIES:
> :HEAGER-ARGS: :session SESS-TEST
> :END:
>
> <> some code in session mode
>
> #+begin_src python
> <...> some code for which
abonnements writes:
> When I write my first post i was using version 8.2.7c.
>
> The behaviour of TAB on an #+name: ligne is the same with 8.2.10
> (installed with package-install from elpa)...
>
> Sorry but can you explain me the normal behavour of TAB.
> Thanks.
#+header: test
#+name: test
When I write my first post i was using version 8.2.7c.
The behaviour of TAB on an #+name: ligne is the same with 8.2.10
(installed with package-install from elpa)...
Sorry but can you explain me the normal behavour of TAB.
Thanks.
Le 26/10/2014 13:42, Nicolas Goaziou a écrit :
abonnements w
Hello,
Rasmus writes:
> It happened to me now when I was editing a table and clicked TAB.
>
> Debugger entered--beginning evaluation of function call form:
> * (byte-code "\301\302\303!\207" [quit-flag t eval (ignore nil)] 2)
> flyspell-post-command-hook()
> recursive-edit()
> debug(error
Hello,
Rasmus writes:
> I think we can do it with titletoc. I have used other functionality
> of titletoc, and it 'doesn't sucks'ᵀᴹ. Below is an example. The
> output is more inline with normal tocs, but you can also style it
> [I've used this for making paragraph-TOCs in the past].
>
> So ox
abonnements writes:
> Thanks, that's what I supposed.
>
> But when you hit "TAB" on a "#+name: " line it fold the block to the
> "#+end_XXX".
> This is not the case for a "#+header:" line.
I think you're using an outdated Org.
> So such a folding stuff may be easy to implement no?
As I wrote a
Hi,
Nicolas Goaziou writes:
> I skipped latex because using minitoc looks too tricky to
> automate.
Sorry, I didn't see this when I posted my other post.
I think we can do it with titletoc. I have used other functionality
of titletoc, and it 'doesn't sucks'ᵀᴹ. Below is an example. The
outpu
Many thanks! I'll wait till this shows up in the package updater (I've
toyed with Git only enough to be dangerous) but am eagerly looking forward
to trying it.
D. C. (Dell Charles) Toedt III *(my** last name is pronounced "Tate") *
Attorney and neutral arbitrator -- tech contracts and intellec
Nicolas Goaziou writes:
> Hello,
>
> "D. C. Toedt" writes:
>
>> I'd like to do sub-TOCs for individual sections and subsections.
>
> We could add a "local" keyword to TOC lines, e.g.,
>
> #+TOC: headlines 1 local
>
> would mean only top level children in current headline.
>
> This feature is t
Thanks, that's what I supposed.
But when you hit "TAB" on a "#+name: " line it fold the block to the
"#+end_XXX".
This is not the case for a "#+header:" line.
So such a folding stuff may be easy to implement no?
Thierry
Le 26/10/2014 11:19, Nicolas Goaziou a écrit :
Hello,
abonnements wri
Hello,
abonnements writes:
> I would like to know if there is, or if it is simple, to have a
> "#+STARTUP: hideblocks" like option which allow to fold named blocks
> leaving only the #+name:
>
> Example
> #+name: test
> #+header: :var foo=10
> #+begin_src python
> ...
> #+end_src
>
> is d
Hello,
I would like to know if there is, or if it is simple, to have a
"#+STARTUP: hideblocks" like option which allow to fold named blocks
leaving only the #+name:
Example
#+name: test
#+header: :var foo=10
#+begin_src python
...
#+end_src
is displayed on the opening of the file folded t
Hi,
I would like to know if it is possible to desactivate a previously
"open session".
Example :
* Test
:PROPERTIES:
:HEAGER-ARGS: :session SESS-TEST
:END:
<> some code in session mode
#+begin_src python
<...> some code for which I dont what to use the session.
#+end_src
Is there somet
Hello,
"D. C. Toedt" writes:
> The local keyword would be great.
The following patch implements local tocs for ascii, html and odt export
back-ends. I skipped latex because using minitoc looks too tricky to
automate.
Feedback welcome.
Regards,
--
Nicolas Goaziou
>From 56e720f11c172b16a72fb
28 matches
Mail list logo
