From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: What is 0.01 here not 0.01 here 0.009999999999999? Date: Sat, 17 Apr 2021 13:53:04 +0300 Message-ID: References: <87o8eehshx.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30733"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0.6 (2021-03-06) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 17 12:59:34 2021 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lXifm-0007tZ-FL for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 17 Apr 2021 12:59:34 +0200 Original-Received: from localhost ([::1]:60466 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lXifk-0003Y6-Hh for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 17 Apr 2021 06:59:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34926) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lXies-0003WJ-Ba for help-gnu-emacs@gnu.org; Sat, 17 Apr 2021 06:58:38 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:38765) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lXieo-0000ZW-Mw for help-gnu-emacs@gnu.org; Sat, 17 Apr 2021 06:58:36 -0400 Original-Received: from localhost ([::ffff:197.157.0.51]) (AUTH: PLAIN securesender, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 00000000000280CB.00000000607ABF55.000017CF; Sat, 17 Apr 2021 03:58:28 -0700 Mail-Followup-To: help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <87o8eehshx.fsf@zoho.eu> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -3 X-Spam_score: -0.4 X-Spam_bar: / X-Spam_report: (-0.4 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:129017 Archived-At: * Emanuel Berg via Users list for the GNU Emacs text editor [2021-04-16 23:42]> > (rcd-vc-increase-decimal-revision-number "10.12") ; 10.129999999999999 > > Indeed, good question... > > It is a binary thing, how floats are implemented. That is solved, it increases now, but that is just one way for versioning. We do not know if it will be versioning for Emacs Lisp, it just small feature, insignificant. I rather think of changing also the Version: line inside of Emacs Lisp automatically with the update. > In your case, if you want a version number that is > MAJOR.MINOR.PATCH what you can do is have them integer > integer integer and then a separate function to output them > > (format "%d.%d.%d" major minor patch) Not that I personally want it at this moment. > I prefer to use the time of change for versions, but that's > just me - and what a horrible world it would be, if everyone > was the same - and for larger/join projects it should/could > be extended, but still, check out: You see, I have that, for now new versions of a file are stored in a database, and the database table has its column named `vc_datemodified', more important there is also the automated unique ID or sequence in the database that always increases. It just does not have adjacent order, but has increasing order of numbers. The completion candidates then look as this: Click on a completion to select it. In this buffer, type RET to select the completion near point. Possible completions are: /home/data1/protected/Programming/emacs-lisp/rcd-cf.el ID: 06899 [6899] /home/data1/protected/Programming/emacs-lisp/rcd-cf.el ID: 06900 [6900] /home/data1/protected/Programming/emacs-lisp/rcd-cf.el ID: 06909 [6909] /home/data1/protected/Programming/emacs-lisp/rcd-cf.el ID: 06913 [6913] The ID is enough, but it is possible to list completion candidates by date, it would be trivial to get that function. SQL is helping in many ways. What I would like now to do as next is finding the previous revisions of particular function by its name no matter where it is located in a file. I would find that useful. Interaction would be to just press a key and get previous versions of the same function for comparison. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns Sign an open letter in support of Richard M. Stallman https://stallmansupport.org/ https://rms-support-letter.github.io/