From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Vincenzo Pupillo Newsgroups: gmane.emacs.bugs Subject: bug#55163: 29.0.50; master 4a1f69ebca (TICKS . HZ) for current-time broke lsp-mode Date: Thu, 28 Apr 2022 22:42:25 +0200 Message-ID: <12000250.O9o76ZdvQC@zarathustrawsp500> References: <87sfpxxyvb.fsf@3-191.divsi.unimi.it> <87zgk5jtm6.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16124"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 55163@debbugs.gnu.org To: Lars Ingebrigtsen , Paul Eggert Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Apr 28 22:43:21 2022 Return-path: Envelope-to: geb-bug-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 1nkAyv-00044k-4D for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 28 Apr 2022 22:43:21 +0200 Original-Received: from localhost ([::1]:59676 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkAyt-0003kT-Ky for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 28 Apr 2022 16:43:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37094) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkAyc-0003h5-2V for bug-gnu-emacs@gnu.org; Thu, 28 Apr 2022 16:43:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56217) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nkAyb-000186-Pw for bug-gnu-emacs@gnu.org; Thu, 28 Apr 2022 16:43:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nkAyb-0006kg-NB for bug-gnu-emacs@gnu.org; Thu, 28 Apr 2022 16:43:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Vincenzo Pupillo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 28 Apr 2022 20:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55163 X-GNU-PR-Package: emacs Original-Received: via spool by 55163-submit@debbugs.gnu.org id=B55163.165117855425899 (code B ref 55163); Thu, 28 Apr 2022 20:43:01 +0000 Original-Received: (at 55163) by debbugs.gnu.org; 28 Apr 2022 20:42:34 +0000 Original-Received: from localhost ([127.0.0.1]:50111 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkAyA-0006jf-6u for submit@debbugs.gnu.org; Thu, 28 Apr 2022 16:42:34 -0400 Original-Received: from mail-ej1-f48.google.com ([209.85.218.48]:40767) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkAy9-0006jS-EF for 55163@debbugs.gnu.org; Thu, 28 Apr 2022 16:42:33 -0400 Original-Received: by mail-ej1-f48.google.com with SMTP id l18so11809904ejc.7 for <55163@debbugs.gnu.org>; Thu, 28 Apr 2022 13:42:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=oaMojmUl8S2hM36U/LiusFVE8MDok5McanAP0gyAZ4I=; b=LLOVc+pKt8nynWR5Q4/4lqEvXt5xYkmxX6sB+yVfvhbQWL/ysq8u8+5AkvGk2Qh4VR Ak0uYsJAjk1gnxbL2Vpa27Ah4PV4iH0wbL3GUZgKosTe/5EaXJNn7p6iJNf3Z5B5wAfA jyPIVGo2cFeuUox8hbEaNGe0k6yDZ+eTENgRfjcjQh1yrEP3Mb4j9coXKCHvVaLCQ4uJ D1EpVYG0J/fErRvCib2DueS4UM7VLkJ8823dUgerZYvBQ1BVhMPCLHZ2XuAi/Y+wbBNn vR9/14UuJACpSs2rpvvYt/VftnTlpznMGAm6oV+zTRcJrUWynZL/31gDZKHfyCR/xP4W 1gcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=oaMojmUl8S2hM36U/LiusFVE8MDok5McanAP0gyAZ4I=; b=5WWZ/E1sQKqlNVuu5tPPjudRrMIzBIjtwsrkzcwO3A/AagAHRrwLvgm9qm5cbJU7qc 6DTwAmyUji7R4ZxJDX+x00YQBdVIE5HNGYcsx3C6iVN5PzRXiNZrX7mEgD+JNr0en0fm ANo7woSIPuKDURTi9bsMUZN7jw+SXiLPjBwNl9/HYH1w/irsXTAXxMTmBV5m3yXlAHIc 8VUWyxEHFodkQSw4j2msBOK1E9uaZk8PqHRZQOk4tnIyHuQO0djxlyU1UWSHXSdfdfYf moDa2E5zVMPcP3lk4WQ6MICmADljjpCfbEJFAIw79eDJ1KjtKPmBNbluvNehxcuK4SZy vJYw== X-Gm-Message-State: AOAM5311XQ8qp3zcMkeTrifP3fbpguWfuKTFnYbJ0QKkEIvgZlv8pqoh 0vrZCzbYj8ArvtM5dzbpcoU= X-Google-Smtp-Source: ABdhPJy9jTL1FRoL88PhMux6tTwtvCbqAGJ0C4mk3eqbC0luyxhuonUVsG0q1p7jrFkbsAKRuzzynQ== X-Received: by 2002:a17:907:2bde:b0:6f3:8e91:3a60 with SMTP id gv30-20020a1709072bde00b006f38e913a60mr22498470ejc.434.1651178547497; Thu, 28 Apr 2022 13:42:27 -0700 (PDT) Original-Received: from zarathustrawsp500.localnet (93-37-156-1.ip66.fastwebnet.it. [93.37.156.1]) by smtp.gmail.com with ESMTPSA id jl22-20020a17090775d600b006f3ef214d9esm8667ejc.4.2022.04.28.13.42.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Apr 2022 13:42:27 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:230913 Archived-At: In data gioved=EC 28 aprile 2022 22:15:54 CEST, Paul Eggert ha scritto: > On 4/28/22 05:10, Lars Ingebrigtsen wrote: > > Paul, it seems like this change is just breaking too much code out > > there, so I think it'll have to be reverted. >=20 > Yes, I came to pretty much the same conclusion. I installed the attached > patch to revert the effect of the change. Instead, this patch adds a new > variable current-time-list that lets you try out the new timestamp > behavior, with the default being the longstanding behavior. >=20 > This was separate from the long thread we had about exposing > clock_getres results to the user, as it doesn't involve calling > clock_getres; it's merely about timestamp format. >=20 > Also, I notice that current-cpu-time was recently added; I'll try to > spring some time free to look into it and will follow up on Bug#44674. Thanks guys, now it works correctly with this patch. Ciao