From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: Efforts to attract more users? Date: Fri, 09 Jul 2010 13:24:43 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1278696325 28085 80.91.229.12 (9 Jul 2010 17:25:25 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 9 Jul 2010 17:25:25 +0000 (UTC) Cc: Juanma Barranquero , "emacs-devel@gnu.org" To: Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 09 19:25:23 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OXHKD-0000ph-IK for ged-emacs-devel@m.gmane.org; Fri, 09 Jul 2010 19:25:21 +0200 Original-Received: from localhost ([127.0.0.1]:36435 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OXHKC-0004Rc-SS for ged-emacs-devel@m.gmane.org; Fri, 09 Jul 2010 13:25:20 -0400 Original-Received: from [199.232.76.173] (port=38953 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OXHJe-0004AC-Pq for emacs-devel@gnu.org; Fri, 09 Jul 2010 13:24:46 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1OXHJd-0005oh-05 for emacs-devel@gnu.org; Fri, 09 Jul 2010 13:24:46 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:46312) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1OXHJc-0005od-Of for emacs-devel@gnu.org; Fri, 09 Jul 2010 13:24:44 -0400 Original-Received: from dann by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1OXHJc-0000lT-3S; Fri, 09 Jul 2010 13:24:44 -0400 User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:126961 Archived-At: Lennart Borgman writes: > On Fri, Jul 9, 2010 at 7:05 PM, Dan Nicolaescu wrote: >> Lennart Borgman writes: >> >>> On Fri, Jul 9, 2010 at 6:09 PM, Dan Nicolaescu wrote: >>>> Lennart Borgman writes: >>>> >>>>> On Fri, Jul 9, 2010 at 2:58 PM, Juanma Barranquero = wrote: >>>>>> On Fri, Jul 9, 2010 at 13:41, Lennart Borgman wrote: >>>>>> >>>>>>> If you want to I can send you the latest working version of >>>>>>> emacsclient.c and so we can perhaps start where we left off. >>>>>> >>>>>> No, as long as it is totally "reordered" wrt the trunk's version. >>>>> >>>>> The reordering is done exactly to make emacsclient.c start Emacs when= needed. >>>>> >>>>> So I do not understand what you ask for. >>>> >>>> I don't have the context for what you are talking about, what code are= you trying to merge? >>>> But emacsclient.c is 1800 lines in trunk now, there's no complicated a= lgorithms in there. >>>> It shouldn't be that complicated to use narrow-to-defun and merge func= tion by function... >>> >>> >>> I would be very glad if anyone has time to try to merge my version and >>> the trunk version. >>> >>> My version is in two parts, the general part and the w32 part. I >>> divided it this way to make the merge easier. Please take the files >>> here, maybe make a temporary bzr repository for those two files and go >>> ahead: >> >> You might want to first explain why would we want to merge your version. >> >>> =A0 http://ourcomments.org/Emacs/DL/C/ >> >> There's some files there with some non-suggestive names (-my.c, >> -my-ok.c) and there's nothing that explains what changes where made >> and why... >> >> It looks like you would be the best person to do the merge... Given >> that there's not that much code, it can't take more than a couple of >> hours. > > I am in a hurry right now. I think any .c versions are ok to start with. > > No, I am not the right person. I have suggested this to this list > before and it was not accepted. Someone else should do it. You might want to try again, and first start by explaining what the new code does and why the changes were needed. Otherwise it's hard to convince anyone to work on code without knowing why... This still says that you are the most qualified to do the work... You can start in small steps: - identify new functions that you added, add those to the end of the file - identify functions that you've changed, merge changes one by one, and write ChangeLog entries explaining the change