From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Carlos Pita Newsgroups: gmane.emacs.bugs Subject: bug#33959: Date: Thu, 3 Jan 2019 01:40:00 -0300 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1546490356 23159 195.159.176.226 (3 Jan 2019 04:39:16 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 3 Jan 2019 04:39:16 +0000 (UTC) To: 33959@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Jan 03 05:39:12 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1geumm-0005x8-4G for geb-bug-gnu-emacs@m.gmane.org; Thu, 03 Jan 2019 05:39:12 +0100 Original-Received: from localhost ([127.0.0.1]:49083 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1geuos-00087x-NH for geb-bug-gnu-emacs@m.gmane.org; Wed, 02 Jan 2019 23:41:22 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:57008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1geuoj-00087j-SU for bug-gnu-emacs@gnu.org; Wed, 02 Jan 2019 23:41:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1geuoZ-0008BX-OZ for bug-gnu-emacs@gnu.org; Wed, 02 Jan 2019 23:41:08 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:46397) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1geuoZ-0008Ar-3W for bug-gnu-emacs@gnu.org; Wed, 02 Jan 2019 23:41:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1geuoX-0001PB-Se for bug-gnu-emacs@gnu.org; Wed, 02 Jan 2019 23:41:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Carlos Pita Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 03 Jan 2019 04:41:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 33959 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 33959-submit@debbugs.gnu.org id=B33959.15464904215332 (code B ref 33959); Thu, 03 Jan 2019 04:41:01 +0000 Original-Received: (at 33959) by debbugs.gnu.org; 3 Jan 2019 04:40:21 +0000 Original-Received: from localhost ([127.0.0.1]:45151 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1geuns-0001Nw-O7 for submit@debbugs.gnu.org; Wed, 02 Jan 2019 23:40:20 -0500 Original-Received: from mail-yb1-f179.google.com ([209.85.219.179]:36935) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1geunq-0001Ng-Hh for 33959@debbugs.gnu.org; Wed, 02 Jan 2019 23:40:18 -0500 Original-Received: by mail-yb1-f179.google.com with SMTP id 2so11077031ybw.4 for <33959@debbugs.gnu.org>; Wed, 02 Jan 2019 20:40:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=i0MryV1YR+VOU/m2uziOW3lrnDby9Mdhw+zP356ry2c=; b=W7wSkSJNW/I0Na2BasyvWtOu2wABvoVYL31DZf+ZuxUOQAcXG60NXIMBze/pt3atoi gcoulNu8JjQz0YZ3Ozx6k6mHASr//p0InV8McsGU1wbm/bKIlH1S7Ona3aydpGCoog7r SvgRlGA+fRg7MpiGbinMrQjRgCzw28J8g3fxa/H3RBEdLdrDFss2dzSp9C9Ye1XnvgY8 mTWSGFH6qSp7qw7UPu54cEckq4P/Xj4EoQhoTV5NYd5Pqj056NdJVwLFlLEf2KF7gSFC ui3nvpGAr87Hovkibm3lqCdKL9NhlkrGjbaXdW2g3Jz7tGKEjgsF0bMv58CGdXa5Klij VcOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=i0MryV1YR+VOU/m2uziOW3lrnDby9Mdhw+zP356ry2c=; b=seAvAV/Gx19y1UYydRF3Ia9LXsu20OyJDeQJ+wSq1LKGUA4Ta1V28JRM8XZfAZebr+ 7gERp/rDezds+Arbl5sxG+9B9czcivLUVSZcX06mK4q/rIfCgPRcdhhkKkSDAVC3/9lr L8UhAZKblt+lEoEHx7uE5J+wpa14UpyiPAlQky02AuDjeyZEpw7mBZftht5bjxdKFU/2 4NescKxt1HbvNoKkatNVFMs4uFMS9swxTuW4mlaEn4f9sdS+gOpJcmZCdgMtEGNGpfNW yH16frrq9EnJpdAoAJTBy3JPEf0iU/zRPzncvpfPgVgXK9IXmemT9XKuV3DnvH1F7MN3 2yWg== X-Gm-Message-State: AJcUukewP/KK0YqQ1Yk+uaNDUMWo824oSJkDwS70QSY8BaZPUAj4bvT3 Lbv0X80Pf0vK+uqrwLwxnK28xtXboGmEcSb07z5ckZi4 X-Google-Smtp-Source: ALg8bN4AaYE2nA0CAktPzMqBwPMIx5sH3siW0kDVfCVDluCUhZjzbLgsGAhSn3UPp4MNu93scnb76cNbLyNntkPQ+UA= X-Received: by 2002:a25:7ec5:: with SMTP id z188mr13719913ybc.282.1546490412504; Wed, 02 Jan 2019 20:40:12 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:154103 Archived-At: Well, I think I was right both times but because the problem is more complex than I thought at first. When I was editing the font lock buffer itself, it was eldoc that was adding an extra line. But when I was editing the shell buffer line, it was company that was adding those lines to the font lock buffer (probably because of a weird effect of an empty menu or something invisibly opening and adding content to the shell buffer). Btw, company is disabled in the font lock buffer since the globalized mode is off for buffers whose name starts with a whitespace: (defun company-mode-on () (when (and (not (or noninteractive (eq (aref (buffer-name) 0) ?\s))) .... The first effect (eldoc) is simple to fix by just disabling eldoc in the font lock buffer, but this is not even necessary since it requires the user to directly edit the font lock buffer in order to trigger it, and this is not a relevant use case. For the second effect (company) I propose to delete from the beginning of buffer each time instead of from the beginning of line, since the font lock buffer won't contain multiline input in any case. Currently after each change in the current line this is being done: (delete-region (line-beginning-position) (point-max)) but I see no reason to not call (erase-buffer) altogether. Do you?