From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 82C4E138330 for ; Thu, 22 Sep 2016 18:28:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DE576E08E1; Thu, 22 Sep 2016 18:28:38 +0000 (UTC) Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 35B43E0881 for ; Thu, 22 Sep 2016 18:28:37 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id wk8so31670870pab.1 for ; Thu, 22 Sep 2016 11:28:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=weFTcLeKt+IKRl3O/HuefxXpDyj0Fo8Sflhci57guFU=; b=eQttFI0zED3+VAmqyyXU8i4P4FCIstd+j78mInVzthA5Y1+6IWVhm6je5HuNtDpYR5 anP1LBsXOZg9UApOc8ohVkUrYQKeE1ZT8yEMOfSrI4g0hLj3Atih0hAAVUZ1ESDMNf6O zTYkCiXSUXbJ2M4TKltiVBUf4858IhetDtxwJ2JKz3fP6qCTs7TuZm1YaxW+DvEmLTCa JfXs7lWiHdWrZ7Y7gvVRCmH51mxmRu5SiuEBJ1c+7Ugc2CEWO+X4fVXhGIKMduEd/P6u LpmcgVN1fz6pLDLCIFd93Xa/H+LKu5uKWRE98OQbrfJdmbjie2N+GfUQhfL6BciTgU3l iv1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=weFTcLeKt+IKRl3O/HuefxXpDyj0Fo8Sflhci57guFU=; b=ia627BIgB212un7RhAwGsF9tyQIieezCBMSIrObdhbGQ3KcXO1/D4lUzzEAzNdkpgp M3p5nXhnfmlAv7OZPNUtb0nYz+cz7XJ0Yxc2roeFeR+nMVYMdTczGzWmW3+b9V1iIubj NJqfZrUT435FAXuIHVD9UpyGvT5BI21YkpDcN98ENtk7s4n8bdQ9qN3sbt6HONIjv32V Yb9qXZWSwwaoFXr7nTZNboJas9oi8oLBROfW5j/bs6KvvzkWpu2JijupRs6HI7xqLLlb Ou9mNCr39aa6d4V7Nf96w8T0oOUP5PTze9/y2/dToMCyluDipw2/Q03x4Vs6VixouGcJ 9wvQ== X-Gm-Message-State: AE9vXwOQZKg1e5ez8dYvMWUD6L+2FTIgKXNx8lZ+5kcxuK8JyxRTSuE3wjeIVdR9CaNKOA== X-Received: by 10.66.160.99 with SMTP id xj3mr5596393pab.73.1474568916514; Thu, 22 Sep 2016 11:28:36 -0700 (PDT) Received: from [192.168.247.60] (76-10-184-45.dsl.teksavvy.com. [76.10.184.45]) by smtp.googlemail.com with ESMTPSA id w15sm5707731pfi.68.2016.09.22.11.28.35 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2016 11:28:35 -0700 (PDT) Subject: Re: [gentoo-user] Vim puts command in when starting up To: gentoo-user@lists.gentoo.org References: <3ac9aa33-84d3-85ca-91b0-2a5906c24016@gmail.com> <20160922161742.GA29438@mgpc.ncp.de> From: Daniel Frey Message-ID: <8832de12-4ce7-f39a-334e-a7ab632ebbaf@gmail.com> Date: Thu, 22 Sep 2016 11:28:34 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20160922161742.GA29438@mgpc.ncp.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: 76843c01-9296-4299-b433-2cd3591a9bb3 X-Archives-Hash: 0f80b1037bbb220fcbeb4e48c0f51279 On 09/22/2016 09:17 AM, Matthias Gerstner wrote: > Hi, > >> For some reason, on one box, whenever I start vim it puts >> ":0000/0000/0000" on the command line. I've looked in vimrc and can't >> see any reference to this. Hitting Enter yields "E486: Pattern not found >> :0000" > > I've had a similar issues for the past months with my vim. It was > related to my using the "urxvt" terminal and its TERM variable being set > to "rxvt-unicode". > > In my case the effect didn't always show up but only under certain > conditions. I remember having seen a bug report for vim back then but > can't seem to find it right now. There are similar, older bug reports, > however, like this one: > > https://bbs.archlinux.org/viewtopic.php?id=199362 > > I also remember there was a bugfix to vim back then to fix the issue. > But the version containing the bugfix was not yet stable in portage and > so I've lived with the occasional bug until now. I'm currently using > vim-7.4.769 and I think the bugfix was contained just a few micro > versions later if I'm not mistaken. Hmm, I've just upgraded to vim v8 and it is still doing it. I'm quite confused. Dan