From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Clocking in on non-org files
Date: Sat, 16 Aug 2014 17:02:05 +0200 [thread overview]
Message-ID: <877g285vgy.fsf@gmail.com> (raw)
In-Reply-To: 20140816164241.56f5b3e3@aga-netbook
Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
> Dnia 2014-08-16, o godz. 16:01:39
> Thorsten Jolitz <tjolitz@gmail.com> napisał(a):
>
>> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>>
>> >> I'm editing this file, C-c C-x C-i just starts clocking.
>>
>> > I finally had some time & motivation to look into it. Below is my
>> > solution.
>>
>> This almost works with outshine.el (use head of tj-outshine branch).
>
> Do I get it correctly (I don't know outshine) that it means that you
> have the actual Org entry /in the same file/, in the comments? If
> yes, this is not really what I'm after.
The outshine idea is rather that your programming-mode file IS (kind of)
your Org file (i.e. programming-mode/org-mode are just two different
views on the same file, and with outorg you can easily switch between
them). You structure it like an Org file, only with outcommented
headers. And then (-> outline-minor-mode/outshine activated) you can do
a lot of things you are used to do in an Org buffer => "Org-mode outside
org-mode" (the major-mode).
--
cheers,
Thorsten
next prev parent reply other threads:[~2014-08-16 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 12:07 Clocking in on non-org files Marcin Borkowski
2013-10-06 15:11 ` Suvayu Ali
2013-10-06 21:26 ` Marcin Borkowski
2014-08-16 12:12 ` Marcin Borkowski
2014-08-16 12:31 ` Marcin Borkowski
2014-08-16 13:47 ` Marcin Borkowski
2014-08-16 14:37 ` Marcin Borkowski
2014-08-16 14:01 ` Thorsten Jolitz
2014-08-16 14:42 ` Marcin Borkowski
2014-08-16 15:02 ` Thorsten Jolitz [this message]
2014-08-16 15:13 ` Marcin Borkowski
2014-08-16 15:35 ` Thorsten Jolitz
-- strict thread matches above, loose matches on Subject: below --
2013-10-06 7:56 Marcin Borkowski
2013-11-05 17:16 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877g285vgy.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).