Sujet : Re: Python (was Re: I did not inhale)
De : david.brown (at) *nospam* hesbynett.no (David Brown)
Groupes : comp.unix.shell comp.unix.programmer comp.lang.miscDate : 15. Sep 2024, 21:47:13
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vc7dk2$2a405$6@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
User-Agent : Mozilla Thunderbird
On 14/09/2024 09:59, Janis Papanagnou wrote:
On 29.08.2024 21:36, David Brown wrote:
On 29/08/2024 18:44, Janis Papanagnou wrote:
On 29.08.2024 14:30, David Brown wrote:
On 29/08/2024 09:28, Muttley@dastardlyhq.com wrote:
[...]
>
Then don't use vim - use an editor that suits your needs.
[...]
>
But what makes you think that his needs are not covered by Vim?
>
You seem to have missed the point - sorry if I was not clear.
>
He complained that he didn't want to learn complicated macros in Vim
just to be able to indent or un-indent lines of code. The solution is
obvious - he should use an editor other than Vim.
This is not what I'd call a solution. I'd call it elusion; and in both
senses - if he didn't use his editor for that space-indenting because
he doesn't know how to do it he could look that up, but it is not any
issue to do that, only more laborious than indenting brace structures,
and the suggestion to switch to another tool is also elusive because
it doesn't address the issue (he would still have to learn how to do
it in any other tool). - But that was not the point.
This thread died out two weeks ago, and should have been left there.
I didn't suggest he switch to a different tool - I suggested he /didn't/ switch to a tool that he didn't want to learn. But I do think it is worth learning some of the basic features of the tools you use regularly.
That is all completely independent of what anyone likes or dislikes about a particular aspect of any particular language.