From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Kastrup Subject: Re: Harmful LESS flags Date: Thu, 24 Apr 2014 21:50:06 +0200 Message-ID: <87ppk6a4nl.fsf@fencepost.gnu.org> References: <4dc69237123e8962b2b2b901692ea78e.id@mailtor> <87lhuvb9kr.fsf@fencepost.gnu.org> <87tx9ia5zq.fsf@fencepost.gnu.org> Mime-Version: 1.0 Content-Type: text/plain Cc: d9ba@mailtor.net, git@vger.kernel.org To: Junio C Hamano X-From: git-owner@vger.kernel.org Thu Apr 24 22:20:38 2014 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WdQ8M-0004hi-4u for gcvg-git-2@plane.gmane.org; Thu, 24 Apr 2014 22:20:38 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752160AbaDXUUe (ORCPT ); Thu, 24 Apr 2014 16:20:34 -0400 Received: from fencepost.gnu.org ([208.118.235.10]:53601 "EHLO fencepost.gnu.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751250AbaDXUUd (ORCPT ); Thu, 24 Apr 2014 16:20:33 -0400 Received: from localhost ([127.0.0.1]:52644 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WdQ8G-0007SN-JZ; Thu, 24 Apr 2014 16:20:32 -0400 Received: by lola (Postfix, from userid 1000) id 2D56FE0989; Thu, 24 Apr 2014 21:50:06 +0200 (CEST) In-Reply-To: (Junio C. Hamano's message of "Thu, 24 Apr 2014 12:29:21 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Junio C Hamano writes: > David Kastrup writes: > >> Junio C Hamano writes: >> >>> Traditionally, because the tool grew in a context of being used in a >>> project whose participants are at least not malicious, always having >>> to be on the lookout for fear of middle-of-line tabs hiding bad >>> contents near the right edges of lines has never been an issue. >> >> My beef is not with "hiding bad contents" but with "hiding contents". >> It makes the output useless for seeing what is actually happening as >> soon as the option starts having an effect. > > My suspicion is that one of the reasons why S was chosen to be in > the default was to mildly discourage people from busting the usual > line-length limit, but I am not Linus ;-) Except that the busting becomes less rather than more conspicuous. -- David Kastrup