From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacsclient startup messages Date: Tue, 26 Oct 2021 15:18:12 +0300 Message-ID: <83h7d4yo6z.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15236"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Pedro Andres Aranda Gutierrez Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 26 14:22:10 2021 Return-path: Envelope-to: ged-emacs-devel@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 1mfLT0-0003ez-97 for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Oct 2021 14:22:10 +0200 Original-Received: from localhost ([::1]:43974 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mfLSz-0000u2-65 for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Oct 2021 08:22:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48184) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mfLPL-0007e9-4n for emacs-devel@gnu.org; Tue, 26 Oct 2021 08:18:24 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53612) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mfLPH-0002aA-0p; Tue, 26 Oct 2021 08:18:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=nJGYjExaeCiazbQP0bYOABEQv/efrXmqIiGGpZ622vg=; b=HVqJI42MhWmU xB8KBgYwPc/HHIjXmRpW27oejIu/UdKzK4WDrgTg6HTSxRLEClSCar0llrHQ5vWwumSq9erXxIJ/7 twBhSNvfUFJrOk/gEuCX/pS5Nf1CWUMcwuh1jG7q02vdfKp+/mFNgMOX+is4yJMIP7/2oCpCB/NDn Pe1HBf4fb5w2tnP7cEnVKJsEkEo2zy7/TsJRb/RXiWnaSI3xzyCv87L5DagNaFn2rOzCybL74zAU6 KBi5bYljc6jqGWap+xIYsKXh3+r1ZEtu0gz2edRerXIdCu+ZK7eWSj0uaYtyWJktLZpclLlJSIhEO ilFlBqGOgMa2whmu3ggNrA==; Original-Received: from [87.69.77.57] (port=1670 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mfLPE-0008PO-DL; Tue, 26 Oct 2021 08:18:18 -0400 In-Reply-To: (message from Pedro Andres Aranda Gutierrez on Tue, 26 Oct 2021 07:26:35 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:277840 Archived-At: > From: Pedro Andres Aranda Gutierrez > Date: Tue, 26 Oct 2021 07:26:35 +0200 > > I was used to the > emacsclient: can't find socket; have you started the server? > emacsclient: To start the server in Emacs, type "M-x server-start". > messages and, despite finding them somehow annoying, well I could live with them :-) > > Lately, this has grown to > emacsclient: Should XDG_RUNTIME_DIR='/run/user/1000' be in the environment? > emacsclient: (Be careful: XDG_RUNTIME_DIR is security-related.) > emacsclient: can't find socket; have you started the server? > emacsclient: To start the server in Emacs, type "M-x server-start". > in my Linux system and, well, it starts being too much... > > even with a emacsclient -q there is no way to silence > emacsclient: Should XDG_RUNTIME_DIR='/run/user/1000' be in the environment? > emacsclient: (Be careful: XDG_RUNTIME_DIR is security-related.) > > If I say quiet, I mean quiet and that should include this message... more so if they ask me maybe do > something that maybe I shouldn't because it is security related... That's not what -q is meant to do. From the --help display: -q, --quiet Don't display messages on success IOW, it isn't supposed to suppress warning, only verbose messages about _successful_ actions. > Isn't there any other way of saying this in a more positive way so that I either decide to take action or not? > Could'nt we also silence this warning in -q? How about redirecting stderr to /dev/null?