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: Sat, 30 Apr 2022 15:22:12 +0200 Message-ID: <8229750.NyiUUSuA9g@zarathustrawsp500> References: <87sfpxxyvb.fsf@3-191.divsi.unimi.it> <3233184.5fSG56mABF@zarathustrawsp500> <83a6c291mr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14563"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, eggert@cs.ucla.edu, 55163@debbugs.gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 30 15:23:20 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 1nkn4C-0003Zz-73 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 15:23:20 +0200 Original-Received: from localhost ([::1]:38140 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkn4A-0003KR-DZ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 09:23:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54754) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkn3u-0003KH-LE for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 09:23:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33987) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nkn3u-0005DJ-Bu for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 09:23:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nkn3u-0005UH-6G for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 09:23:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Vincenzo Pupillo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 30 Apr 2022 13:23:02 +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.165132494221032 (code B ref 55163); Sat, 30 Apr 2022 13:23:02 +0000 Original-Received: (at 55163) by debbugs.gnu.org; 30 Apr 2022 13:22:22 +0000 Original-Received: from localhost ([127.0.0.1]:56117 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkn3F-0005TA-T0 for submit@debbugs.gnu.org; Sat, 30 Apr 2022 09:22:22 -0400 Original-Received: from mail-wr1-f46.google.com ([209.85.221.46]:34474) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkn3E-0005Sr-3k for 55163@debbugs.gnu.org; Sat, 30 Apr 2022 09:22:21 -0400 Original-Received: by mail-wr1-f46.google.com with SMTP id q23so14080074wra.1 for <55163@debbugs.gnu.org>; Sat, 30 Apr 2022 06:22:20 -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=3uIxuj8skSVUFjXgzfML/p28Qwi/rc0hHCYWDzrXPfQ=; b=i5S9f5faZYq6uVNplDDQqg7wMUnGYAEh45y8JaYfRd9+M8TL8ijtQIMQEDQl0CQgtD a5XfGdtOwzr7rUXBZDjr4KUZ1zvBtaQdY+67yFOqTTQ8hBf0TLMYb0VaHS6nuRz66Wad 4m09A/DNuSZdpTyyE/0EQl5DqobwDLbL2gFSLyo0bY3XwtZzOxXc/ALEdWNYHEbFGSwt EaHwW2xD3aixFzScs71Gj+6E74iDCQdqT4LctQBvUVqC6yoMiRwULPWMyyhbQ/2Htn4M zEAbV+FsOfA74/58VRPWOsm1THV0fBTAQFiaYC+foftEnp55pjD50Q053rXfXvZkoO08 I5FA== 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=3uIxuj8skSVUFjXgzfML/p28Qwi/rc0hHCYWDzrXPfQ=; b=oY7n+KKJCGcoOlo4fuBQjbphWSHT62WmYUggiIJGS9WvDgOTiJIo9zidJdj1DyGxXA sS8AuQ0ij12fw8dOU3amwA+iydl3+6w0P4WkzJYNbCSCh8QZo4IRRb2yT5YTCuLXjLL3 7WSjcdzG/HdZwDX6veWeGZYjVg3+/Q+WfbK1VKteTaUMpxFi+OdbTgGFPMAsCLvNLXQ6 NWM4tFmsUjHXOJIAQMT2eRFdkEGuPBe6RGkXTWShsnF+Jc1WXL+Mkfu2JI4SofsnrlQ4 bJ8h6SsAPjY1YONhAHiKYmbeC7nFE5ES5A6t6W8jvErZKZwXcMyAlSZ8jl1A5Wea989g kVbw== X-Gm-Message-State: AOAM5322waqQYz5vOff7e0xU4sZgIgVJATsFx5onSz5NxnvoGUzl3RI0 hjkU8Q1dFQbpg0tDgeTD0xU= X-Google-Smtp-Source: ABdhPJzUjFjUvLAdewd02T3DMm5823/2lfuNhK1mO6M5u3g0scOvBOfdWGG9oWHwZvyCZ8oK1jiDmw== X-Received: by 2002:a5d:6c65:0:b0:20c:5230:f145 with SMTP id r5-20020a5d6c65000000b0020c5230f145mr2975091wrz.337.1651324934130; Sat, 30 Apr 2022 06:22:14 -0700 (PDT) Original-Received: from zarathustrawsp500.localnet (93-43-201-114.ip93.fastwebnet.it. [93.43.201.114]) by smtp.gmail.com with ESMTPSA id l2-20020adfb102000000b0020c547f75easm1653026wra.101.2022.04.30.06.22.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 30 Apr 2022 06:22:13 -0700 (PDT) In-Reply-To: <83a6c291mr.fsf@gnu.org> 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:231029 Archived-At: In data sabato 30 aprile 2022 14:50:04 CEST, Eli Zaretskii ha scritto: > > From: Vincenzo Pupillo > > Cc: eggert@cs.ucla.edu, larsi@gnus.org, 55163@debbugs.gnu.org, > > monnier@iro.umontreal.ca Date: Sat, 30 Apr 2022 14:32:17 +0200 > > > > > > Many packages on melpa/elpa have a custom log function. I'm not > > > > familiar > > > > with the Emacs API, is there a standard way to log events? > > > > I think a simple log function would be useful for many packages. > > > > > > Do you mean logging to the system log? > > > > > > If not, then generating a log doesn't require any new primitives, I > > > think, you could just use write-region or something? > > > > > > Or am I misunderstanding the feature you have in mind? > > > > I mean something that can generate a properly formatted log message, in a > > "standard" way (with log levels, ERROR, WARNING, INFO etc, if possible), > > for both use cases if possible. Something like log4j, but not as > > monstrous as log4j. > > Sure, why not? Because log4j does too many things, and I think it's too much for emacs. I think something simpler is enough.