On Wed, 05 Apr 2017 21:16:42 +0200, Axel Berger wrote:

> Martin Gregorie wrote:
>> Thats fine if you aren't working on a developer team and never intend
>> to share your code with other people.
>
> A team usually has a set style of how things ought to be done.
>
Indeed, and doing something like the search-and-destroy mission on all
tabs in programs is usually quite a good way of getting slung off the
team.

>> or keep them, filed against the text file's pathname on some sort of
>> cache,
>
> So of you need to set it manually, you only need to do it once. What is
> so bad about a comment as the first line of the file? If the source is
> to be shared or to be reused by yourself some time later a few
> explanations there won't come amiss anyway.
>
Granted its better than doing it with editor configuration because it
does at least stay with the file. I've only see that done once in what |I
suppose you could describe as a proto-IDE, and from memory contained
rather more than just a tab setting line - it also contained the sort of
compilation directives that C programmers expect to find in a Makefile.


--
martin@   | Martin Gregorie
gregorie. | Essex, UK
org       |

--- SoupGate-Win32 v1.05