Gnus development mailing list
 help / color / mirror / Atom feed
From: Leonidas Tsampros <ltsampros@upnet.gr>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Tutorials and worg like site for gnus.
Date: Wed, 30 Mar 2011 20:32:48 +0300	[thread overview]
Message-ID: <87aagcbjjz.fsf@bifteki.lan> (raw)
In-Reply-To: <87d3l8d95g.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 30 Mar 2011 08:34:35 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:
> On Wed, 30 Mar 2011 22:09:55 +0900 Yagnesh Raghava Yakkala <yagnesh@live.com> wrote: 
>
> YRY> One of the other list I am following is orgmode. I could at least get
> YRY> familiar with internal parts of org. Org has a very good website and as
> YRY> you all might know Worg written by the community, is fantastic, many
> YRY> tutorials which are helping me a lot to get start with different parts.
>
> YRY> So I think it would be great to have such a system for Gnus as well to
> YRY> open the doors to newcomers, given the fact that different backends,
> YRY> that complex terminology, and networking stuff make people scare off.
>
> I think it's better to wait for Cloudy Gnus before mounting this kind of
> effort.  It is very likely to materially change backend subscriptions,
> marks, and the other things that currently make configuring Gnus hard;
> tutorials and docs would have to be rebased and that's a lot of work.
>
> Ted

While I've been trying to keep myself as far as possible from git-gnus
(It's not for the faint hearted), it would be very much intresting to
see what will Cloudy Gnus has to offer from a feature perspective and
what old functionality is expected to break.

Eventually, at some undefined (to me, that is) time in the future, the
new Cloudy Gnus will hit the bzr emacs trunk which I follow, and thus
if something breaks, I have to be in brace-for-impact-mode.

Is there any comprehensive list of things that WILL be changed and are
expected to break in the near future with regards to the standard
functionality that is already offered by Gnus?

p.s. reading the cloudy-gnus thread a while back did not help me
understand the spirit of this effort -- noticing that I'm totally biased
for local mail.

Leonidas Tsampros



  reply	other threads:[~2011-03-30 17:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 13:09 Yagnesh Raghava Yakkala
2011-03-30 13:34 ` Ted Zlatanov
2011-03-30 17:32   ` Leonidas Tsampros [this message]
2011-03-30 18:48     ` Ted Zlatanov
2011-03-30 19:02       ` Leonidas Tsampros
2011-03-30 19:11         ` Ted Zlatanov
2011-03-30 19:32           ` Leonidas Tsampros
2011-03-30 21:07             ` Ted Zlatanov
2011-03-30 20:22       ` Steinar Bang
2011-03-30 20:24       ` Steinar Bang
2011-03-30 18:14 ` Lars Magne Ingebrigtsen
2011-03-31 15:11   ` Yagnesh Raghava Yakkala
2011-03-30 18:41 ` Leonidas Tsampros
2011-03-31 16:56   ` Yagnesh Raghava Yakkala
2011-03-31 18:46     ` Leonidas Tsampros
2011-04-01 18:39       ` Yagnesh Raghava Yakkala
2011-03-31 19:49     ` Eric S Fraga
2011-04-01 18:46       ` Yagnesh Raghava Yakkala
2011-04-01 19:06         ` Eric S Fraga

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87aagcbjjz.fsf@bifteki.lan \
    --to=ltsampros@upnet.gr \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.com \
    /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.
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 NNTP newsgroup(s).