headers
Bastien | 1 Aug 2010 01:52
Picon
Favicon

Re: Patchwork: Patch 176 Accepted

Hi Tassilo,

Tassilo Horn <tassilo <at> member.fsf.org> writes:

>> Patch 176 (http://patchwork.newartisans.com/patch/176/) is now Accepted.
>> 
>> This relates to the following submission:
>> 
>> http://mid.gmane.org/%3C87fwz4159y.fsf%40thinkpad.tsdh.de%3E
>
> Oh, I didn't notice that this patch was grabbed by patchwork.  

Yes, every (correctly) attached patch is grabbed by patchwork.

I misread your email and thought the correctED patch was the 
correct one...  sorry for that.

I reverted the patch.

Thanks,

--

-- 
 Bastien

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
(Continue reading)

Permalink | Reply | 0 comments |
headers
Typhoon | 1 Aug 2010 02:56
Picon
Favicon

Re: Footnote export

On Sat, 31 Jul 2010 19:33:14 +0200
Jan Böcker <jan.boecker <at> jboecker.de> wrote:

> On 07/31/2010 08:32 AM, Typhoon wrote:
> > 
> > Yes, thanks. I was using f:nil but what I would really like is to
> > disable [1] type footnotes while retaining the [fn:1] style.
> > 
> > Nice trick on the zero-space - That would be OK, I suppose, but like
> > you say, a bit tedious after a while.
> > 
> 
> Alright, so we know a way to do what we want (although it is possibly
> not the most elegant method), but it is a tedious, repetitive task. No
> worries, that's what computers are for!
> 
> Add the following to your .emacs:
> 
> (defun jb/disable-plain-footnotes-hack ()
>   (if (plist-get opt-plist :no-plain-footnotes)
> 	  (save-excursion
> 		(goto-char 1)
> 		(replace-regexp "\\[\\([0-9]+\\)\\]" "[\u200B\\1]"))))
> 
> (add-to-list 'org-export-inbuffer-options-extra
> '("DISABLE_PLAIN_FOOTNOTES" :no-plain-footnotes))
> 
> (add-hook 'org-export-preprocess-hook
> 'jb/disable-plain-footnotes-hack)
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Sexton | 1 Aug 2010 03:02
Picon

[ANN] Org-Drill: Interactive revision a la Anki/Mnemosyne

Announcing the first release of "org-drill", a module which uses "org-learn" to
present interactive "drill sessions" of marked material in org buffers and
files. Org-learn, which is found in org's "contrib" directory, is an
implementation of the spaced repetition algorithm from SuperMemo.

Repository:
http://bitbucket.org/eeeickythump/org-drill

See the preamble in org-drill.el, and the accompanying file "spanish.org", for
documentation and examples. 

I have tried to make it quite customisable. You can set variables to control
number of items per session, and max session duration. You can also create
custom "card types" and write elisp functions to control how the information in
those topics is displayed.

Note that org-learn currently considers items rated 4 or 5 (ie perfect or
excellent recall) as NEVER needing to be revised. I think this is a misfeature
of org-learn, and I hope it will eventually be fixed. For now, if you use
org-drill and rate items as 4 or 5, org-drill will consider them as "new" each
time you rpeat the drill session, so they will always come up. 

Paul

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
(Continue reading)

Permalink | Reply | 3 comments |
headers
Erwin Panen | 1 Aug 2010 15:47

MobileOrg - One step further

Hi,

Thanks to numerous helpfull instructions from Richard Moreland, I'm 
trying to take MobileOrg one step further.

Here's what I try to do:
- I've setup MobileOrg on 3 devices: My Mac, my winXP machine and my iPad.

At first I wanted stuff to work between my MacBook and the iPad, as most 
required stuff is present on the Mac by default. (md5sum)
Next, I've updated my XP Orgmode version to be the same as my Mac's 
(6.36trans) On my XP machine, I have Emacs on a USB 2 1/2" harddisk, and 
I've added these lines to my .emacs file:
------------------------------------
;; MobileOrg
(setq org-mobile-directory "C:/Documents and Settings/erwin/My 
Documents/My Dropbox/MobileOrg")
(setq org-mobile-inbox-for-pull "~/git/org/from-mobile.org")

;; Checksumming
(setq org-mobile-checksum-binary "K:/winpack/msys/bin/md5sum.exe")
------------------------------------

Now all seems well, and I was really wondering how multi-device syching 
would behave. I'm not sure if it's supposed to function at all, and 
would welcome any practical experience from other users reading this.

So I created a simple new-tasklist.org file with a couple of TODO items
I did this on the Mac, and took care to have only new-tasklist.org in 
the agenda files.
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Maus | 1 Aug 2010 14:50
Picon

Re: TODO type problem on speedbar and imenu.

Osamu OKANO wrote:
>[1  <text/plain; ISO-8859-1 (7bit)>]
>Hi.
>I found a problem on speedbar and imenu.
>Reproducing date is here
>-8<---------------cut here---------------start------------->8---
>* someday/maybe
>* SOMEDAY/maybe
>* SOMEDAY maybe
>* someday maybe
>* read/review
>* READ/review
>* conf
>#+TYP_TODO: SOMEDAY
>--8<---------------cut here---------------end--------------->8---

>When a head line includes TODO state name,
>I am afraid that displayed head line names on speedbar are wrong.
>Because SOMEDAY is TODO type but "someday/maybe" and "SOMEDAY/maybe"
>is not TODO task.

I can confirm this with Org-mode version 7.01trans
(release_7.01g.26.g24bb.dirty) on GNU Emacs 23.2.1 (i486-pc-linux-gnu,
GTK+ Version 2.20.0) of 2010-05-16 on raven, modified by Debian.

 -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena <at> jabber.org
Email..... dmaus <at> ictsoc.de
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Maus | 1 Aug 2010 10:58
Picon

Re: [PATCH] Add support for multile html container classes.

Bastien wrote:
>Hi David,

>David Maus <dmaus <at> ictsoc.de> writes:

>> * org-html.el (org-html-level-start): Add multiple container
>> classes.

>I don't quite understand this patch.

>Can't we use

>  :PROPERTIES:
>  :HTML_CONTAINER_CLASS: class1 class2 class3
>  :END:

>already?

No: Org currently only uses the first class.  E.g.

,----
| (re-search-forward "^[ \t]*:HTML_CONTAINER_CLASS:[ \t]+\\(\\S-+\\)" nil t)
| (setq class (match-string 1))
`----

\\S-+ matches only the first sequence of non-space characters.

>PS: Also, please make sure the patch only reflect changes in the code
>(avoid refilling), it makes it easier to read ;)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Thierry Volpiatto | 1 Aug 2010 10:19
Picon
Gravatar

info:annotation in Emacs bookmarks with org

Hi all,
you can use now annotation feature of Emacs bookmarks with org if you
use bookmark-extensions.el.

http://mercurial.intuxication.org/hg/emacs-bookmark-extension/

--

-- 
Thierry Volpiatto
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Permalink | Reply | 0 comments |
headers
Bastien | 1 Aug 2010 11:33
Picon
Favicon

Re: [PATCH] Add support for multile html container classes.

Hi,

David Maus <dmaus <at> ictsoc.de> writes:

> No: Org currently only uses the first class.  E.g.
>
> ,----
> | (re-search-forward "^[ \t]*:HTML_CONTAINER_CLASS:[ \t]+\\(\\S-+\\)" nil t)
> | (setq class (match-string 1))
> `----
>
> \\S-+ matches only the first sequence of non-space characters.

Okay - I've checked it a simpler version, allowing sequences with white
chars to be matched as the HTML_CONTAINER_CLASS.

>>PS: Also, please make sure the patch only reflect changes in the code
>>(avoid refilling), it makes it easier to read ;)
>
> Okay, I'll try to remember to provide separate patches for this.

Thanks!

--

-- 
 Bastien

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode <at> gnu.org
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andreas Röhler | 1 Aug 2010 18:40
Picon

Re: Re: keys and command name info

Am 01.08.2010 11:42, schrieb Bastien:
> Hi Andreas,
>
> Andreas Röhler<andreas.roehler <at> easy-emacs.de>  writes:
>
>> please permit pointing at the silliness of such approaches, which state
>> a creative work starts upward from 10 lines.
>>
>> No single haiku will ever have a change to be protected by that famous
>> US-copyright law.
>>
>> I'm against spreading stupidity over the world and see with sorrow
>> people abiding to it.
>
> I'm not following the US copyright law here, but Emacs contribution
> policies:
>
> ,----[ etc/CONTRIBUTE ]
> | * Copyright Assignment
> |
> | We can accept small changes (roughly, fewer than 15 lines) without
> | legal papers.  Anything more substantial requires a copyright
> | disclaimer or assignment (the latter is preferred, especially for
> | larger changes).  Both of these involved filling out a short form and
> | filing it with the FSF.  The process is straightforward -- contact us
> | at emacs-devel <at> gnu.org to obtain the relevant forms.
> `----
>
> It's not a matter of the change being trivial or not -- but of course,
> it's even more frustrating not being able to apply your patch if it's
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bastien | 1 Aug 2010 11:42
Picon
Favicon

Re: Re: keys and command name info

Hi Andreas,

Andreas Röhler <andreas.roehler <at> easy-emacs.de> writes:

> please permit pointing at the silliness of such approaches, which state
> a creative work starts upward from 10 lines.
>
> No single haiku will ever have a change to be protected by that famous
> US-copyright law.
>
> I'm against spreading stupidity over the world and see with sorrow
> people abiding to it.

I'm not following the US copyright law here, but Emacs contribution
policies:

,----[ etc/CONTRIBUTE ]
| * Copyright Assignment
| 
| We can accept small changes (roughly, fewer than 15 lines) without
| legal papers.  Anything more substantial requires a copyright
| disclaimer or assignment (the latter is preferred, especially for
| larger changes).  Both of these involved filling out a short form and
| filing it with the FSF.  The process is straightforward -- contact us
| at emacs-devel <at> gnu.org to obtain the relevant forms.
`----

It's not a matter of the change being trivial or not -- but of course,
it's even more frustrating not being able to apply your patch if it's
trivial :)
(Continue reading)

Permalink | Reply | 1 comment |

Gmane