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: An anonymous IRC user's opinion Date: Tue, 19 Nov 2024 21:01:08 +0200 Message-ID: <8634jnt5e3.fsf@gnu.org> References: <867ca9shcw.fsf@gnu.org> <7cb15f5c-efd0-4516-8190-a53c0d958eb6@gutov.dev> <86ses8x1po.fsf@gnu.org> <865xp3w64u.fsf@gnu.org> <61171da3-7428-4572-bc13-783766a123b5@gutov.dev> <86v7x2u7rz.fsf@gnu.org> <86msidubg4.fsf@gnu.org> <867c9htwt7.fsf@gnu.org> <387887a4-ba19-485e-8805-d1aabe2058ff@gutov.dev> <86y11xsbil.fsf@gnu.org> <17465b85-430a-4e91-8b12-769b60181ada@gutov.dev> <86ses4sglw.fsf@gnu.org> <86fro4sddd.fsf@gnu.org> <6ac73c67-cb2d-48ef-8f1d-683c5335aba5@gutov.dev> <8634k4s2r2.fsf@gnu.org> <082b0388-b3a1-4523-9f9b-5ead4b110e11@gutov.dev> <86plmrtemx.fsf@gnu.org> <7aa4a684-3374-4d0f-8efc-c4df29337c5e@gutov.dev> <86cyirtahu.fsf@gnu.org> <556779b3-9308-4fd3-9050-bf9c49658cd1@gutov.dev> <864j43t8t9.fsf@gnu.org> <4cc676e8-cac5-4348-99b0-243baf74687e@gutov.dev> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1848"; mail-complaints-to="usenet@ciao.gmane.io" Cc: johan.myreen@gmail.com, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 19 20:02:00 2024 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 1tDTU8-0000ID-KI for ged-emacs-devel@m.gmane-mx.org; Tue, 19 Nov 2024 20:02:00 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tDTTO-0000jp-90; Tue, 19 Nov 2024 14:01:14 -0500 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 1tDTTL-0000jZ-Me for emacs-devel@gnu.org; Tue, 19 Nov 2024 14:01:12 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tDTTL-0001sJ-1c; Tue, 19 Nov 2024 14:01:11 -0500 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=EapeX5j0AhFHBp60p8PQ/L3HxDJyNJX/nqeU/M6EopU=; b=VQLkvYt3Zjl+ 5FcQ8jP5XX+uJMAm08JRSA7yQ0qce6Wb9bETySmNcDlLM+O0KjbxrEC5FJJHpwE9wJIcXNEWaz739 2ocd+6RvAY2oNo8VUxKI73SJTuD/s1MefM9s0/v7NyoWfSQ4i3+LRqMsoglRN8OOQMBO7FH5v3ZhV I8nVTEBvVl5gspJ5RRzE3ur27qUMuWacuisNPHU+zI4nirkWty0vtI0ozEgNAk90MhIEmYiM/rd0C gk160G1OTBwTrLs3JX7yLtVxvZ2nxHFE3r2/3sjqKj4TnvX7YuRqO3sPiHU/QbNOuEfb9pgztsDFm Zw7tmOacACsVqVZg+1wCPA==; In-Reply-To: <4cc676e8-cac5-4348-99b0-243baf74687e@gutov.dev> (message from Dmitry Gutov on Tue, 19 Nov 2024 19:56:05 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:325513 Archived-At: > Date: Tue, 19 Nov 2024 19:56:05 +0200 > Cc: johan.myreen@gmail.com, emacs-devel@gnu.org > From: Dmitry Gutov > > > Wasn't the idea that the user will tell us which files she wants to > > visit in each mode? > > I think we talked about making the option more granular (allowing to set > it not just to t, but to a list of modes). That will be easy to add. > > But specifying the files as well is news to me. Wouldn't users who want > that level of detail just go and customize auto-mode-alist instead? Maybe so, but that is not always easy nor user-friendly: getting the regexps right is not trivial, many people make mistakes. And I thought this discussion at some point mentioned that Emacs should suggest a mode for the file being visited? in which case specifying the file is trivial. I'm also not opposed to having the data ready somewhere in advance.