From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Creating a coding system Date: Sat, 20 Dec 2014 21:11:49 +0100 Message-ID: <877fxmgjy2.fsf@fencepost.gnu.org> References: <87ppbeitcs.fsf@fencepost.gnu.org> <87sigasa3n.fsf@igel.home> <878ui2ieu1.fsf@fencepost.gnu.org> <87k31ms3gr.fsf@igel.home> <87zjaigtkz.fsf@fencepost.gnu.org> <83tx0qqn4d.fsf@gnu.org> <87r3vugr1s.fsf@fencepost.gnu.org> <83mw6iqicx.fsf@gnu.org> <87egrugmyi.fsf@fencepost.gnu.org> <83ioh6qeci.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1419106362 24280 80.91.229.3 (20 Dec 2014 20:12:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 20 Dec 2014 20:12:42 +0000 (UTC) Cc: schwab@linux-m68k.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 20 21:12:35 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Y2QO8-0003nE-V4 for ged-emacs-devel@m.gmane.org; Sat, 20 Dec 2014 21:12:33 +0100 Original-Received: from localhost ([::1]:35693 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y2QO8-00042z-62 for ged-emacs-devel@m.gmane.org; Sat, 20 Dec 2014 15:12:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y2QNY-0003bS-6X for emacs-devel@gnu.org; Sat, 20 Dec 2014 15:11:57 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y2QNT-0002Cb-28 for emacs-devel@gnu.org; Sat, 20 Dec 2014 15:11:56 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53344) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y2QNS-0002CX-VF for emacs-devel@gnu.org; Sat, 20 Dec 2014 15:11:50 -0500 Original-Received: from localhost ([127.0.0.1]:60517 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y2QNR-0006Cf-Jw; Sat, 20 Dec 2014 15:11:49 -0500 Original-Received: by lola (Postfix, from userid 1000) id 1059DE056B; Sat, 20 Dec 2014 21:11:49 +0100 (CET) In-Reply-To: <83ioh6qeci.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 20 Dec 2014 22:02:37 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:180406 Archived-At: Eli Zaretskii writes: >> From: David Kastrup >> Cc: schwab@linux-m68k.org, emacs-devel@gnu.org >> Date: Sat, 20 Dec 2014 20:06:45 +0100 >> >> Now the first iteration would be just using the pitches from a Midi >> keyboard. The second iteration would then try working with durations. >> Either by putting time stamps on the events as they trundle in, or by >> reading from a "cooked" Midi stream already containing encoded time time >> stamps. >> >> Conversion of time stamps to musical durations, particularly when the >> time stamps have not been generated by a notation program but by a human >> player, is non-trivial and would hopefully end up as an incremental >> process where a human corrects durations and Emacs improves its overall >> guesswork. >> >> But time stamps are for another time. Right now I'd be glad just to >> convert the pitches from they keyboard into LilyPond's pitch notation in >> order to make key entry faster. > > I might be mistaken, but this doesn't look to me like a job for a > coding-system. You are talking about parsing input into some abstract > notation, "parsing input" is sort of bombastic for interpreting a binary representation consisting of isolated minimal words. > then generating a representation of that input in a different > language. This is sufficiently different from converting characters > from one encoding to another that you should perhaps look at > cedet/semantic/ stuff instead. Uh, there is no grammar involved here, no context, most certainly not a push-down stack or something. There is nothing that would warrant using a parser. And we are talking about real-time processing needs, basically an input method using a different device than the keyboard. cedet/semantic seem like much more of a mismatch, both in functionality and response time, than using a process encoding here. -- David Kastrup