From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37947 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: strangely-placed cursor in summary buffer Date: Sat, 18 Aug 2001 00:28:09 +0200 Organization: Programmerer Ingebrigtsen Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035173610 18208 80.91.224.250 (21 Oct 2002 04:13:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:13:30 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 8537 invoked from network); 17 Aug 2001 22:28:35 -0000 Original-Received: from quimby.gnus.org (195.204.10.139) by gnus.org with SMTP; 17 Aug 2001 22:28:35 -0000 Original-Received: (from news@localhost) by quimby.gnus.org (8.9.3/8.9.3) id AAA21635 for ding@gnus.org; Sat, 18 Aug 2001 00:28:21 +0200 (CEST) Original-To: ding@gnus.org Original-Path: not-for-mail Original-Newsgroups: gnus.ding Original-NNTP-Posting-Host: quimbies.gnus.org Original-X-Trace: quimby.gnus.org 998087301 30006 195.204.10.148 (17 Aug 2001 22:28:21 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 17 Aug 2001 22:28:21 GMT Mail-Copies-To: never X-Now-Playing: His Name Is Alive's _Early Music Vol. 1_: "Still" User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/20.7 X-Face: &w!^oO~dS|}-P0~ge{$c!h\ You could put a text property on the spot where the cursor should go. > Then putting the cursor in the right spot can be done by putting it on > the beginning of the line and then searching for the next change of > that property. > > How about that? Text properties makes things go slower in general. Back when I used to fiddle with such stuff, it seemed like there was some exponential delay in buffer updating with the number of text props there were in the buffer. However, things are better now, aren't they? Perhaps text properties are the right solution here... Hm. I think they are the best solution; yes. It does mean that they'll be sync points when generating the summary lines. That is, where there is now a (format "lotsastuff"), there will be (format "somestuff"), put text prop, (format "somemorestuff"). This performance hit will only, er, hit the people who actually use the %C spec, which is something I like. Ok. %C as a text prop it is... -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen