December 2008 - implementations-list

[implementations-list] Re: vimpulse doesn't work in emacs-snapshot
by Jason Spiro 02 Dec '08

02 Dec '08

2008/12/2 Johannes Kanig <johannes.kanig(a)gmail.com> wrote: > I'm sorry, but I guess I wasn't subscribed to the mailing list yet > when you sent Gu's solution. I am now. Could you resend that solution > to me, please? No need. It is in the archives. :) Go to http://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list then click the "archives" link near the top. Does it work for you? If so: ISTM that it shouldn't help. Why does it help? Please Reply to All.

2 3

[implementations-list] Re: [gnu.org #393190] Dear FSF clerk, here are all my questions about copyright assigment
by Jason Spiro 01 Dec '08

01 Dec '08

2008/12/1 Donald R Robertson III via RT <copyright-clerk(a)fsf.org> wrote: > Hello, > > It is great to hear that you are interested in contributing to Emacs. > There's actually a bit of process for getting your work included in > Emacs that I'm not sure you have gone through yet. If you have, I > apologize. You should go to https://savannah.gnu.org, if you are not > already a member there, then sign up and login. Then go to the Emacs > page, then click on the members list. There is a link there to a form > for requesting inclusion on the project. We won't need to have an > assignment on file until you go through this process and have your work > included. > > Putting your work in the public domain is okay, as such work can be > included in the GNU Project. The only issue really is that proprietary > developers can use your work if it is in the public domain. > > As for the rest of your questions, I think we should just hold off on > them until we know that the work is going to be included. It's better to > have someone take a look at a work before determining whether an > assignment is needed, and that takes a bit of time to do. If the work is > not included in Emacs, then we can about other options you might use to > get your work distributed freely. > > Thanks again for your interest in contributing, and good luck. > -- > Sincerely, > > Donald R. Robertson, III, J.D. > Assignment Administrator > Free Software Foundation > 51 Franklin Street, Fifth Floor > Boston, MA 02110 > Phone +1-617-542-5942 > Fax +1-617-542-2652 Hi Mr. Robertson, No, I have not applied to get either of the two works into Emacs yet. I and others agree it that Vimpulse is too buggy to get into Emacs yet. And I don't care enough about viper-in-more-modes to try to get it into Emacs. But I want to make sure the projects can easily get into Emacs when needed. So I think I will get all the contributors to release their contributions to the public domain. I will probably do so by asking them to go through the clickthrough public domain dedication process at http://creativecommons.org/license/publicdomain-2 and then forward the email receipt they get to the bug tracker. Do you think that is a good and safe method for people to dedicate work to the public domain, that will work no matter what country they come from (e.g. Canada, Italy, China)? If you reply, please make sure to Reply to All. -Jason

1 0

[implementations-list] Fwd: [workaround] vimpulse failed at when referring to my-get-emulation-keymap
by Jason Spiro 01 Dec '08

01 Dec '08

Forwarded conversation Subject: vimpulse failed at when referring to my-get-emulation-keymap ------------------------ From: Gu Yijun <yijun.gu(a)gmail.com> Date: 2008/7/29 To: jasonspiro3(a)gmail.com, laynor(a)gmail.com, brad.beveridge(a)gmail.com I tried vimpulse today and found it incompatible with emacs 23.0.60.1 I compiled by myself from cvs source last week. The error message I get (with or without --debug-init) is "wrong-type argument: symbolp, (my-get-emulation-keymap) and the error completely paralyzed emacs. I do notice that the notice you put in the comments about a similar error, but deleting 'viper--key-maps doesn't work for me. I know very little about lisp, but it seems that the culprit is "viper-normalize-minor-mode-map-alist" just below "my-get-emulation-keymap" but I don't know how to modify it. Do you know what causes the error? btw: the procedure I used in compiling cvs emacs can be found at http://www.najja.org/doku.php?id=it:emacs ---------- From: Gu Yijun <yijun.gu(a)gmail.com> Date: 2008/7/30 To: jasonspiro3(a)gmail.com, laynor(a)gmail.com, brad.beveridge(a)gmail.com I tested vimpulse.el on my windows box with emacs compiled from July 14th cvs source. My solution is to move the "viper-normalize-minor-mode-map-alist" function to .emacs and all seems well. If I just remove the function, cut/copy/paste doesn't work with visual mode.

1 0

[implementations-list] Followup: vimpulse doesn't work in emacs-snapshot
by Jason Spiro 01 Dec '08

01 Dec '08

2008/11/26 Jason Spiro <jasonspiro3(a)gmail.com> wrote: > I don't know, and I don't use emacs 23, and my elisp skills are not so > great. :) Could one of you please subscribe to > http://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list > , then ask the emacs help mailing list for help, and send a CC to > implementations-list? You must be a list subscriber to post to > implementations-list. IIRC the list gets less than five messages per > month. I finally got to dealing with some old emails and noticed that Gu Yijun sent a solution. I will forward it to the mailing list right away. Thank you very much Gu. Johannes and Frank: If you have a chance, please test Gu's solution. Does it work for you? If so: ISTM that it shouldn't help. Why does it help?

1 0

[implementations-list] Dear FSF clerk, here are all my questions about copyright assigment
by Jason Spiro 01 Dec '08

01 Dec '08

Dear FSF copyright assignment clerk, I am the maintainer of two Emacs add-ons: Vimpulse[1] and viper-in-more-modes[2]. Vimpulse is still too buggy to ship with Emacs, and I don't use or care much about viper-in-more-modes so have never even evaluated whether they can ship with Emacs. But I would like to start getting copyright assignments for both add-ons now so that they can ship with Emacs eventually. I care so little about viper-in-more-modes that I will not talk about it in the rest of this email. The rest of this email talks about Vimpulse only. I am not a main contributor. There are two main contributors: Alessandro Piras (in Italy) and Brad Beveridge (I think in Canada). They said they are both willing to sign copyright assignment papers. I have contributed maybe 5 lines of code and dozens of lines of documentation. I have already disclaimed all copyright to my contributions and placed my contributions in the public domain, but I will gladly sign papers too if you like. Question 1: Is it good that I have placed my contributions in the public domain? (I live in Canada.) There have been some other contributors. I have no idea exactly how many; I would have to look at each of the 80 old email threads in my inbox relating to Vimpulse. Maybe I will move them all into the Vimpulse bug tracker at ourproject.org, which is currently empty, for ease of future tracking. The following are estimates based on memories from last year: Some people have contributed one- or two-line fixes. Perhaps half a dozen (or maybe less) people have contributed larger amounts of code: e.g. ten to twenty lines. Question 2: What is the minimum number of lines that requires copyright assignment? (I tried doing a Google search for 'fsf copyright assignment' and found the old document [3] from 'prep' which refers to various files that let me check whether papers have been received and talk more about the various options (assign vs. disclaim) and such. But I couldn't find the files it refers to. It would be wonderful if you could put those files up on the web. Q3: What if someone contributes code which does nothing but define keybindings (keyboard shortcuts)? Q4: Should I include lines of documentation / comments in my count of lines of code? How about blank lines? Q5: There are several unreviewed patches in my inbox. Do you recommend I leave them unreviewed until I have gotten copyright assignment for them? Q6. How about if I tell the pending patch contributors, "Please contact assignments @ gnu.org so you can assign your contributions to the FSF (this is best) or disclaim copyright to your contributions and put them in the public domain (if you are unwilling to assign copyright). After that, please test your patch, and if it tests OK, please merge it into Vimpulse on the EmacsWiki." Please Reply to All. Thanks in advance, --Jason Spiro ^ [1]. http://www.emacswiki.org/elisp/vimpulse.el ^ [2]. http://www.emacswiki.org/emacs/viper-in-more-modes.el ^ [3]. http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html

1 0

[implementations-list] Re: viper-in-more-modes
by Stephen Bach 01 Dec '08

01 Dec '08

On Mon, Sep 17, 2007 at 09:57:26PM -0400, Jason Spiro wrote: > 2007/9/16, Stephen Bach <sjbach(a)comcast.net> wrote: > > On Sun, Sep 16, 2007 at 11:46:47AM -0500, Jason Spiro wrote: > ... > > > Yes but I am looking for a co-maintainer. If you are interested, I'd > > > love it if you could volunteer even a few hours of your time :) > > > > Perhaps - what would be involved? > > Testing patches on Emacs 21, Emacs 22, and/or XEmacs 21. Preferably > all three. :) Sure, I'd be willing to put in a little effort. I'm currently running Emacs 22 and a 23 snapshot. Let me know what I can do. Regards, Steve

2 1