From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: pjb@informatimago.com (Pascal J. Bourguignon) Newsgroups: gmane.emacs.help Subject: Re: underline-line Date: Sat, 26 Dec 2009 00:52:25 +0100 Organization: Informatimago Message-ID: <87637uobly.fsf@hubble.informatimago.com> References: <87k4wc7hru.fsf@Traian.DecebalComp> <87fx70peup.fsf@hubble.informatimago.com> <87pr635zr0.fsf@Traian.DecebalComp> <87tyveirfi.fsf@lion.rapttech.com.au> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1261831645 17379 80.91.229.12 (26 Dec 2009 12:47:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 26 Dec 2009 12:47:25 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Dec 26 13:47:18 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NOW3B-0007LE-C7 for geh-help-gnu-emacs@m.gmane.org; Sat, 26 Dec 2009 13:47:17 +0100 Original-Received: from localhost ([127.0.0.1]:46960 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NOW3B-0004YF-Mb for geh-help-gnu-emacs@m.gmane.org; Sat, 26 Dec 2009 07:47:17 -0500 Original-Path: news.stanford.edu!usenet.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 65 Original-X-Trace: individual.net JSxnpAliGsiTrI/y7BSAJwZWvLtt671w6kwUQzPJA1PUiN2ZsQ Cancel-Lock: sha1:M2RmOTE3NThmY2IxOWY5MWExN2NiOTBiYWFmM2NiMTRjN2M0MTg2OQ== sha1:4/dSrxH3uf6n8xuH64ZPmMfVpnY= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en X-Disabled: X-No-Archive: no User-Agent: Gnus/5.101 (Gnus v5.10.10) Emacs/22.3 (gnu/linux) Original-Xref: news.stanford.edu gnu.emacs.help:175794 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:70871 Archived-At: Tim X writes: > Cecil Westerhof writes: > >> pjb@informatimago.com (Pascal J. Bourguignon) writes: >> >>> Cecil Westerhof writes: >>> There should be no problem with tabs, because there should be not tab >>> in text files. >> >> I do not use them, but I know that other people do. Better to describe >> the consequences then, so that people are not taken by surprise. >> >> >>> The only place where prefix tabs are allowed, for historical reasons >>> is in Makefile. >> >> I know a lot of people who use it for indenting and it is used for >> 'tables'. But maybe I should give a warning when tabs are found in the >> text. >> But maybe I should document the function works with 'clean' text files. > > I personally don't think tabs are a problem What is a problem is when > you get source files that have a mixture of tabs and spaces where they > are not used consistently. > > Using tabs for indent can actuallly be very useful. If I'm working with > a team and we all have different preferences for how large our code > indents are, rather than forcing a standard indent size on all team > members, we can just use tabs and each member can set the tab width to > their preferred indent size i.e. 2 spaces, 4 spaces, 8 spaces etc. C-x h C-M-\ I'd even put the equivalent in find-file-hook... (and possibly the same in save-file-hook with the project parameters). > The problem is when you have some people indenting using spaces and some > using tabs. Then all the indenting gets screwed up. > > I don't have an issue with tabs in Makefiles. The emacs Makefile mode > can show tabs/spaces, so its easy to see when something is wrong/missing > a leading tab. > > I doubt we can change make effectively. There are millions of lines of > makefile code with tabs out there (I was told there are more lines of > Makefile code out there than Ruby). Much of this code is in projects > that are unlikely to have the inclination or resoruces to want to modify > their Makefiles to remove the tabs. Changing make to handle just > generic whitespace (i.e. space or tab) would be possible, but it won't > remove tabs from the equation. We are pretty much stuck with them for > the time being. Makefile:2:warning TAB used instead of space Makefile:3:warning TAB used instead of space Makefile:4:warning TAB used instead of space Makefile:6:warning TAB used instead of space Makefile:7:warning TAB used instead of space ... -- __Pascal Bourguignon__ http://www.informatimago.com/