From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Yves Baumes Newsgroups: gmane.emacs.help Subject: Re: How to follow the end of *Messages* buffer in Emacs? Date: Sat, 10 Nov 2012 23:00:49 +0100 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1352584867 5096 80.91.229.3 (10 Nov 2012 22:01:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 10 Nov 2012 22:01:07 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: martin rudalics Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Nov 10 23:01:17 2012 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TXJ76-0003fP-Qr for geh-help-gnu-emacs@m.gmane.org; Sat, 10 Nov 2012 23:01:16 +0100 Original-Received: from localhost ([::1]:42195 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TXJ6x-0005Dj-50 for geh-help-gnu-emacs@m.gmane.org; Sat, 10 Nov 2012 17:01:07 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:41108) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TXJ6q-00059c-7v for help-gnu-emacs@gnu.org; Sat, 10 Nov 2012 17:01:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TXJ6n-0007dT-5i for help-gnu-emacs@gnu.org; Sat, 10 Nov 2012 17:01:00 -0500 Original-Received: from mail-wg0-f49.google.com ([74.125.82.49]:51216) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TXJ6m-0007dJ-VI for help-gnu-emacs@gnu.org; Sat, 10 Nov 2012 17:00:57 -0500 Original-Received: by mail-wg0-f49.google.com with SMTP id gg4so2399070wgb.30 for ; Sat, 10 Nov 2012 14:00:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=3BXYdFuqmBqopMFaZD86RDU4HYqiNp2Dqikfqq1kak8=; b=ZmhJlog6nEtJXekeKT2Wwcv9F0Y2L20Z+oC/6Ih9LNM/RD4n5ycyjghCjFrmzT/zK6 BRrDnM+ZF3rKT57PhCEDJwtImR1HVXl6hth6p7QTkTLb1iuxCBeuqNqzbFQVf8ouzY5h I/hhtT0aq4KRbT6BBPhCP3+Gh3DqgIPRfS3aURDDYI11IkmlDQfyH+S2VopaLUHJC6np a+mUh+HdnsjNXNYwH9taZmGmEgu1PLiOl/3BR9EVOGd92KP2SfwufVgDudNtEscSJeqj A/g3Re0fFnFe2Pvlrc4Y5bh1pyljDpAYaq3VVqlKDvxTbYmt6kGCggcM0p1iX+Ihb6Ln RfVg== Original-Received: by 10.180.103.201 with SMTP id fy9mr8624922wib.10.1352584855895; Sat, 10 Nov 2012 14:00:55 -0800 (PST) Original-Received: from mac-mini-de-yves-baumes.local.localhost (rke75-2-82-66-91-208.fbx.proxad.net. [82.66.91.208]) by mx.google.com with ESMTPS id eu8sm2686536wib.1.2012.11.10.14.00.53 (version=SSLv3 cipher=OTHER); Sat, 10 Nov 2012 14:00:55 -0800 (PST) In-Reply-To: (martin rudalics's message of "Sat, 10 Nov 2012 22:02:52 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (darwin) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 74.125.82.49 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:87636 Archived-At: martin rudalics writes: > For the moment it should be sufficient if you add your function to > `window-configuration-change-hook' instead of `post-command-hook'. This > should allow you to scroll and edit *Messages* without any problems. I've just tried and it does not work with that hook, as is. I don't know whether it is related to mistakes on my side , or whether it is related to the bug you've highlighted previously. I've added some 'message call to my function in order to try to understand, and obviously the '(point-max) gets a lower value from one execution to the other. Since my *Messages* buffer is not limited in size, it must not happen I presume. (Something tells me it is related to the bug you were talking about, but I still need to re-read your email and digest it in order to get a better picture about what is going on here. :-) ) Yves.