emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tokuya Kameshima <kames@fa2.so-net.ne.jp>
To: emacs-orgmode@gnu.org
Cc: kames@fa2.so-net.ne.jp
Subject: Re: Needless opening of threads in org-wl
Date: Sun, 28 Sep 2008 00:33:37 +0900 ()	[thread overview]
Message-ID: <20080928.003337.86194634.kames@fa2.so-net.ne.jp> (raw)

Dhruv,
Thank you for the report.

The line of (wl-thread-open-all) is needless.  I completely forgot to
remove it.

Carsten,

Could you remove the line of (wl-thread-open-all) from org-wl.el and
update the git repository?

-*-*-

In my initial implementation of org-wl.el, `org-wl-open' was able to
jump to the message by the message number ([[wl:folder#number]]) as
well as by the message id ([[wl:folder#msgid]]).  To jump to the
message by the number, the message line had to be shown in the summary
buffer.  So I added the code to show all the message lines in the
summary buffer.

The current version of org-wl.el does not support the link with the
message number such as [[wl:folder#number]].

Thanks,
--Tokuya


> From: Dhruv Bansal <lasnabvurhd <at> gmail.com>
> Subject: Needless opening of threads in org-wl
> Newsgroups: gmane.emacs.orgmode
> Date: 2008-09-20 10:05:12 GMT (5 days, 13 hours and 37 minutes ago)
> 
> I like to link to Wanderlust emails from Org Mode.  I just downloaded
> the latest git version and linking to WL emails works as advertised
> except that I wind up sitting for five minutes as every thread in my
> 13,000 message inbox is opened.  Is there a reason for this behavior?
> 
> I "fixed" the problem with the following patch which merely comments
> out the command to open all the threads.  Linking emails works
> perfectly fine and now I don't have to wait long at all.
> 
> ================
> diff --git a/lisp/org-wl.el b/lisp/org-wl.el
> index 4fae584..58ddd31 100644
> --- a/lisp/org-wl.el
> +++ b/lisp/org-wl.el
> @@ -135,7 +135,7 @@
>  	;; in the old buffer.
>  	(set-buffer old-buf)
>  	(goto-char old-point))
> -     (wl-thread-open-all)
> +;     (wl-thread-open-all)
>       (and (wl-summary-jump-to-msg-by-message-id (org-add-angle-brackets
>  						  article))
>  	   (wl-summary-redisplay)))))
> ================
> 
> Just thought I'd post this in case anyone else was similarly
> frustrated.
> 
> I'm excited about the new org version; thanks so much everyone for
> helping to create such a great application!
> 
> --
> Dhruv Bansal
> http://www.dhruvbansal.com
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode <at> gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 

             reply	other threads:[~2008-09-27 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-27 15:33 Tokuya Kameshima [this message]
2008-09-27 15:57 ` Re: Needless opening of threads in org-wl Carsten Dominik
  -- strict thread matches above, loose matches on Subject: below --
2008-09-20 10:05 Dhruv Bansal

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=20080928.003337.86194634.kames@fa2.so-net.ne.jp \
    --to=kames@fa2.so-net.ne.jp \
    --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).