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: Copying a list for insertion Date: Sat, 22 Oct 2022 14:23:13 +0300 Message-ID: References: <29DGE8Qruce2adT4VliRagiL6uTUNrtFSw92oYfSUXNYb9vqBg9NghQyFGA13qrkl27rlPcTk0fofL30WVeSoRAhOzXr4KllyNUds2sYGxI=@protonmail.com> <9TXhRJBFzT6P6K1nhsFI3560kqLqmeeNT-AuXamhhGYaCHKQxVOZAt1SM7YoZCzzqR6IBo4G_u6ZtUV3qzkbxHhp5qk9b7g3qZXL41FraaQ=@protonmail.com> <6R3U2YSb8t6P3xDLvwmpxXhIPmoIo5UJRcpqn5HMZrna0CAhcWDiEp4vub3sSjLmwLuNCr08xCMstMteOUPLg5-JKPJj24pcZHqp2DWFH1I=@protonmail.com> <871qr0el8u.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39131"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.2.7+37 (a90f69b) (2022-09-02) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Mon Oct 24 07:28:45 2022 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 1omq0x-0009tv-5l for geh-help-gnu-emacs@m.gmane-mx.org; Mon, 24 Oct 2022 07:28:43 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1omgEr-00072J-3L for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 23 Oct 2022 15:02:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1omE31-0002Qx-JQ for help-gnu-emacs@gnu.org; Sat, 22 Oct 2022 08:56:19 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1omE2y-0006In-Ux for help-gnu-emacs@gnu.org; Sat, 22 Oct 2022 08:56:19 -0400 Original-Received: from localhost ([::ffff:102.82.123.168]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000007DC18.000000006353E86D.00002BCD; Sat, 22 Oct 2022 05:56:12 -0700 Mail-Followup-To: help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <871qr0el8u.fsf@dataswamp.org> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 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:140304 Archived-At: * Emanuel Berg [2022-10-22 14:08]: > Jean Louis wrote: > > >> Any reason why you use "progn" in the "stringp" condition? > > > > (defun rcd-kill-new (kill) > > (cond ((stringp kill) (progn > > (kill-new kill) > > (rcd-message "Killed: %s" kill))) > > (t (rcd-message "😧 WARNING: Nothing to kill.")))) > > > > I use it to enclose two functions in one body of functions > > as `cond' does not allow me to use 2 functions for one > > condition without enclosing. > > (if (not (stringp str)) ... ) `cond' gives me better overview and I often expand conditions in future. Long term, `cond' is more flexible then `if'. > You can also do > > (let ((str (format "%s" data))) ...) > > But as you know there is already `kill-new' ... `advice-add', > maybe that happens all the time tho so you don't want that? > I guess you'll find out. There is `advice-remove'. Aha, well, I can't use `message' as it does not give me specific control over my messages. By changing all occurences of `message' to my specific messaging function, I can then decide what to do with those messages, for example, I can see them in separate buffer. They also go in main message buffer, but I like having my separate buffer. Then I can also choose different buffers for different purposes, having the actual on the fly log for messages that is specific to some package or program. My messaging buffer looks like this: 2022-10-22-14:07:02 RCD DB: updated table `usersdefaults', column `usersdefaults_numberoflatestentries', ID: 1 2022-10-22-14:07:04 Fetching list of people 2022-10-22-14:07:04 Total of 1000 people 2022-10-22-14:08:14 RCD DB: updated table `people', column `people_hyobjects1', ID: 363293 I could as well direct my messages to file for later examination. But if they are all mixed in one main *Messages* buffer, that is not enough useful. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/