unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Wei-Wei Guo <wwguocn@gmail.com>
To: Stefan Merten <smerten@oekonux.de>
Cc: Martin Blais <blais@furius.ca>,
	emacs-devel@gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>,
	David Goodger <goodger@python.org>
Subject: Re: Add a functionality of bullet list and enumeration list to rst.el.
Date: Sat, 27 Nov 2010 00:31:29 +0800	[thread overview]
Message-ID: <4CEFE0E1.5010303@gmail.com> (raw)
In-Reply-To: <11120.1290182752@theowa.merten-home.homelinux.org>

Hi Stefan,

于 2010年11月20日 00:05, Stefan Merten 写道:
> Hi Stefan!
>
> Thanks for contacting us!
>
> 2 days ago Stefan Monnier wrote:
>> Hello rst.el maintainers.  Weiwei Guo submitted a patch to rst.el to
>> improve the handling of enumerated items.
>
> Wei-Wei submitted this or a similar patch a while ago to the docutils
> project. Unfortunately it has not been integrated yet - due to lack of
> time.
>

I submitted a revised patch to Emacs which wasn't submitted to the docutils.


>> It seems OK to me, but since I don't use rst.el my judgment might not
>> be very relevant.  Could you confirm that we should install it?
>
> I'm just preparing a new version of rst.el for the Emacs development.
> It merges the downstream patches from you Emacs developers with a
> couple of improvements I did in the upstream version in the docutils
> version. IMHO it would be wiser that I integrate Wei-Wei's patch in
> the upstream version.
>

I use rst.el every day and my version of rst.el keeps on being modified.
I take submitting patch as a serious thing, so I dare to submit my rough
patch to Emacs or docutils. Since you are preparing a new version, I
prefer send my version of rst.el to you if you want. You can use any code
of mine freely.


>> I have included the original patch as well as an alternative patch which
>> includes additional (untested) changes I made to improve the coding
>> style (and fix an apparent bug in his patch w.r.t handling
>> rst-re-items).
>
> Thanks for this.
>
> I'd suggest this: I'll look at your version of the patch and include
> in the upstream version in the docutils project and then send the
> result to the Emacs developers. I think this would be the best way
> also because in my local development environment I'm maintaining all
> the versions of rst.el I know of so I'm probably the only one who can
> merge all the changes properly. Since I now have an improved version
> of this patch I'll do this immediately. Is that ok for you?
>

Best wishes,
Wei-Wei



      reply	other threads:[~2010-11-26 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 10:34 Add a functionality of bullet list and enumeration list to rst.el Weiwei Guo
2008-12-17 21:18 ` Glenn Morris
2010-11-17 22:30 ` Stefan Monnier
2010-11-19 16:05   ` Stefan Merten
2010-11-26 16:31     ` Wei-Wei Guo [this message]

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=4CEFE0E1.5010303@gmail.com \
    --to=wwguocn@gmail.com \
    --cc=blais@furius.ca \
    --cc=emacs-devel@gnu.org \
    --cc=goodger@python.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=smerten@oekonux.de \
    /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.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).