From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alexis Newsgroups: gmane.emacs.help Subject: Re: customizing minibuffer and the message bar, ie mode-line Date: Mon, 20 Apr 2015 10:54:54 +1000 Message-ID: <87iocrd3fl.fsf@gmail.com> References: <682e54d4-38b9-49ad-8e3b-0e7ab4451bdb@googlegroups.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Trace: ger.gmane.org 1429491316 22294 80.91.229.3 (20 Apr 2015 00:55:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Apr 2015 00:55:16 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Apr 20 02:55:16 2015 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 1YjzzX-0005qH-LW for geh-help-gnu-emacs@m.gmane.org; Mon, 20 Apr 2015 02:55:15 +0200 Original-Received: from localhost ([::1]:51380 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjzzX-0003t0-2U for geh-help-gnu-emacs@m.gmane.org; Sun, 19 Apr 2015 20:55:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjzzM-0003rj-Th for help-gnu-emacs@gnu.org; Sun, 19 Apr 2015 20:55:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YjzzJ-0006av-NM for help-gnu-emacs@gnu.org; Sun, 19 Apr 2015 20:55:04 -0400 Original-Received: from mail-pd0-x22b.google.com ([2607:f8b0:400e:c02::22b]:35574) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjzzJ-0006aj-EX for help-gnu-emacs@gnu.org; Sun, 19 Apr 2015 20:55:01 -0400 Original-Received: by pdbqd1 with SMTP id qd1so191000286pdb.2 for ; Sun, 19 Apr 2015 17:55:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:to:subject:in-reply-to:date:message-id:mime-version :content-type; bh=hlTatJb4H0ehd3RaeVMiHEMFx/HTC5Ss2QO/o4NSoWA=; b=K2H3ikVqKYhQnlFomspoxJSS71ss2fafWVTVevxrt/ShXC4Q7LMABFzh/ZAt+QTGv6 gqmr+yJgIKsstrIH1QYjh25msJIA0m6FcoazovzU7WII1yr4LjFivj3rY/UvvqpPASi1 4TNhDn/GRBSW37r42HbxCubVA0bc2Vnumjt65Kru3Gf/sbt/05ba4yGw51k25F2sW9Uv cdmcj7zH3YQTMnizdLI5KICeoEo83TQhG3ZcDqD2q2qgN5cReuCb7Tuzaj9BvegP15gK zhOrB5qFlXtZjhwWy8VK7Bw6Blw+AaHzznYIyqrLqYDdQH/2nP4SGT4ieR8Fn/VQseu2 pv1Q== X-Received: by 10.66.189.105 with SMTP id gh9mr23271720pac.41.1429491300367; Sun, 19 Apr 2015 17:55:00 -0700 (PDT) Original-Received: from localhost (ppp118-209-46-94.lns20.mel4.internode.on.net. [118.209.46.94]) by mx.google.com with ESMTPSA id su5sm16247729pbc.38.2015.04.19.17.54.58 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 19 Apr 2015 17:54:59 -0700 (PDT) In-reply-to: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c02::22b 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:103875 Archived-At: gnuist006@gmail.com writes: > why dont you also reply (1) and (2) ? People respond to the questions they feel they can address, and don't necessarily respond to the questions to which they feel they can't provide a reasonable answer. Having said that, one thought regarding question 2: >> (2) How to make time up to the second in the message bar? i assume you want the clock visually displaying each second as it elapses. If so, this might not be straightforward, as the mode-line is not updated on a regular schedule, but "when appropriate" (e.g. point has been moved). So say the clock displayed: 12:24:48 and nothing caused the mode-line to update for 10 seconds (e.g. there was no buffer input), then the next mode-line update would cause the clock to 'jump' to: 12:24:58 without having displayed the intervening seconds. i guess you might be able to set up a timer to run every second to deal with this; but more knowledgeable people than i on this list would be better placed to discuss the feasability of that. Alexis.