Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103775 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 63314 invoked from network); 22 Jan 2019 19:11:52 -0000 Received: from unknown (HELO mail-lj1-f179.google.com) (209.85.208.179) by pb1.pair.com with SMTP; 22 Jan 2019 19:11:52 -0000 Received: by mail-lj1-f179.google.com with SMTP id g11-v6so21058492ljk.3 for ; Tue, 22 Jan 2019 07:49:32 -0800 (PST) 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:cc; bh=MMYEDEYOYj8QswsiVw6l39nXLhhMteKPpzD2NuVsOjg=; b=Jk8trluJOfYaQNprrUy8KjV60PY0BhT5Zt5GvtzMkAqaeufjEMu8Cjcczjh7bSR5YY UJ4OtNfVKkUUo3GP2mAb+YvKqqB2c1pISlnSmgRxSVmeNWLDPY4V0beXZMEoRXrjzFjg m6dGTow/oVgZDsip240tO1G7pFJ66KmaBNgGHAOxVgs1yQuA4vtizxJJ7lhwaRCGNPpw 5AzgZD0sBRwPtPy+KljTHhqffanTv1MqnLok2hvtl7g6nqGCXqh8R+f6C05pqZtJ9A80 lSYC9x4TNj4rXsT5nTHp/ElVxKIYCqFYtpBjUS0BE2I1rS+EgKw1inZD00PK2ihopszG ZdRw== X-Gm-Message-State: AJcUukcOcNe3/8OM5Vx6ZXM7eAbXbNzoEarpdTzsABDBCtiMVH2ZxmXR t69mL0aJSPGQw1jBG1XggUBolWsxxUSQoePRrm0= X-Google-Smtp-Source: ALg8bN52uo4N2lxjKm+tPh7QGKlR0Uo0OUpkfnTWRW9N20SP9+mQcqt1Ahi35jOwHbbsdsPAtaITrWIEkfkFJfu1PxU= X-Received: by 2002:a2e:9783:: with SMTP id y3-v6mr20379512lji.167.1548172171520; Tue, 22 Jan 2019 07:49:31 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 22 Jan 2019 08:49:14 -0700 Message-ID: To: Peter Kokot Cc: Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Local variables for editors From: levim@php.net (Levi Morrison) On Wed, Nov 29, 2017 at 2:54 PM Peter Kokot wrote: > > Hello, > > I'm not sure if this has been discussed before, but I find these local > variables in C, H and other files a bit strange and bloated: > > /* > * Local variables: > * tab-width: 4 > * c-basic-offset: 4 > * End: > * vim600: noet sw=4 ts=4 fdm=marker > * vim<600: noet sw=4 ts=4 > */ > > Is there any chance to start omitting them and use a single > .editorconfig file instead or is this something that is a must have in > C projects of today? > > Thank you for some clarification on this :) > -- > Peter Kokot > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php I use vim, and do not enable these per-file settings. I don't think any distributions enable them by default either. My opinion: I think we can get rid of them. I have used .editorconfig and .clang-tidy for other projects and liked it. I tried using it with tabs, and the experience seemed less polished but still worked.