From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: blink-cursor frame parameter Date: Sun, 17 May 2009 17:30:17 -0400 Message-ID: References: <004001c9d732$07d81c70$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1242595839 14489 80.91.229.12 (17 May 2009 21:30:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 17 May 2009 21:30:39 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 17 23:30:32 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1M5nwF-0006Qv-Nc for ged-emacs-devel@m.gmane.org; Sun, 17 May 2009 23:30:32 +0200 Original-Received: from localhost ([127.0.0.1]:46023 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M5nwF-00021V-1o for ged-emacs-devel@m.gmane.org; Sun, 17 May 2009 17:30:31 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M5nw8-00021G-Ib for emacs-devel@gnu.org; Sun, 17 May 2009 17:30:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M5nw4-0001xH-EP for emacs-devel@gnu.org; Sun, 17 May 2009 17:30:24 -0400 Original-Received: from [199.232.76.173] (port=45256 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M5nw4-0001x2-7Z for emacs-devel@gnu.org; Sun, 17 May 2009 17:30:20 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:25424 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M5nw3-0001i3-Qd for emacs-devel@gnu.org; Sun, 17 May 2009 17:30:19 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvAFAC4fEEpMCovv/2dsb2JhbACBT81bhAEFhWo X-IronPort-AV: E=Sophos;i="4.41,208,1241409600"; d="scan'208";a="38713847" Original-Received: from 76-10-139-239.dsl.teksavvy.com (HELO ceviche.home) ([76.10.139.239]) by ironport2-out.teksavvy.com with ESMTP; 17 May 2009 17:30:18 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id A79D070017; Sun, 17 May 2009 17:30:17 -0400 (EDT) In-Reply-To: <004001c9d732$07d81c70$0200a8c0@us.oracle.com> (Drew Adams's message of "Sun, 17 May 2009 13:57:02 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.93 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:110955 Archived-At: > There doesn't seem to be a frame parameter that corresponds to whether > and how the cursor blinks. > Other modes, such as menu-bar-mode, tool-bar-mode, scroll-bar-mode, > and fringe-mode all act via a frame parameter. > Why not blink-cursor-mode also? AFAIK, scroll-bar-mode and fringe-mode frame parameters are mostly historical errors (they should be either window parameters or buffer-local settings). menu-bar-mode and tool-bar-mode refer to frame-level entities, so it makes sense to configure them on a frame-by-frame basis. Since there can be several cursors per frame, `blink-cursor-mode' should be per-window or per-buffer. Not sure if setting it buffer-locally works, but it's not terribly important since AFAIK either users want it to blink everywhere or nowhere. Stefan