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: Printf and quoting in general, SQL injection in particular [was: Emacs Modular Configuration: the preferable way] Date: Tue, 22 Jun 2021 18:45:56 +0300 Message-ID: References: <87pmwgdiyj.fsf@zoho.eu> <83y2b3tq07.fsf@gnu.org> <871r8vcrnm.fsf@posteo.net> <20210621141148.GA29347@tuxteam.de> <20210621211547.GA12274@tuxteam.de> <87pmwevjbs.fsf@zoho.eu> <83bl7yumh1.fsf@gnu.org> <8335taujt6.fsf@gnu.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="10386"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0.7+183 (3d24855) (2021-05-28) Cc: help-gnu-emacs@gnu.org To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jun 22 18:05:31 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 1lviu2-0002U6-Ms for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 22 Jun 2021 18:05:30 +0200 Original-Received: from localhost ([::1]:36184 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lviu1-0006BX-Ma for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 22 Jun 2021 12:05:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57666) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lvigK-0002AZ-Ip for help-gnu-emacs@gnu.org; Tue, 22 Jun 2021 11:51:20 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:56657) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lvigI-0006kt-G9; Tue, 22 Jun 2021 11:51:20 -0400 Original-Received: from localhost ([::ffff:197.157.0.61]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000075C65.0000000060D206F1.00000B57; Tue, 22 Jun 2021 08:51:12 -0700 Mail-Followup-To: Eli Zaretskii , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <8335taujt6.fsf@gnu.org> 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:131199 Archived-At: * Eli Zaretskii [2021-06-22 16:11]: > We _represent_ file names as strings, but they are not normal strings. > Just like characters are represented as integers, but they are not > just simple integers, they have additional special attributes and > behaviors. I get your point, what I don't agree with is the Formulierung. It is for same reason as you mentioned it, people are reading our writings and our form or text should be possibly clear. If you wish to say they are not normal strings, demonstrate it. By demonstration below it shows to be of type string. What is else there? I have a file: ~/tmp/new.txt This works fine: (find-file "~/tmp/new.txt") ⇒ # Is it normal string? (type-of "~/tmp/new.txt") ⇒ string Of course I know there are functions that will get file attributes, and those are fine. Of course that meanings of strings are so much different. But subject was that we deal with strings in those functions. It was not about the meaning of strings. I have functions which chunk human names in 3 parts. Functions use strings. It really does not matter that I want to parse the human names and chunk it or fit it into some form, or do something with it. It does not change the type of a string and fact that strings are supplied to functions. The function `file-attributes' gives some different type as a result: (file-attributes "~/tmp/new.txt") ⇒ (nil 1 1001 1001 (24786 1053 990790 326000) (24786 1033 720790 188000) (24786 1033 720790 188000) 0 "-rw-r--r--" t 51912267 65024) (type-of (file-attributes "~/tmp/new.txt")) ⇒ cons Then we can work on that with: (setq attributes (file-attributes "~/tmp/new.txt")) (file-attribute-size attributes) ⇒ 0 (file-attribute-status-change-time attributes) ⇒ (24786 1033 720790 188000) I do understand you wish to point out to functions which interpret and represent the meanings. It still did not change the fact that string was supplied to it: "~/tmp/new.txt" Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/