removal of master/slave terminology from vim source code

[Mike Fulton]

Hi,

I would like to propose removing the master/slave terminology from the vim source code and replacng it with more inclusive, and hopefully more accurate, terminology.

I am open to suggestions for the right terms to use.

The particular area that I see most occurrences in is the 'pty' code.

How about using controller/controlled instead of master/slave (or perhaps controlling/controlled?) ?

I would be happy to develop and test the patch. I believe this would strictly be changes to variable names but I would need to do a more thorough check to see if there are any externals.

Thanks, Mike Fulton

[Dominique Pellé]

I'm no expert on pty, but master/slave seems to be the
proper terminology. I e.g. see it here:

https://man7.org/linux/man-pages/man7/pty.7.html
https://en.wikipedia.org/wiki/Pseudoterminal

I understand that there is a trend to replace for example
the master branch by the main branch in git repos as
some people feel offended by the terminology. But frankly,
there is no reason to be offended by a word when its
meaning clearly depends on the context. There was
clearly not ill intention in the terminology. And renaming
causes problems to users and to existing scripts. Now
when I'm in a git repo, I no longer know whether I need
to checkout from master, or main, or trunk, or dev, or
root, or unicornbranch (...) as it depends on each project.

Regards
Dominique

[Bram Moolenaar]

Mike Fulton wrote:

> I would like to propose removing the master/slave terminology from the vim
> source code and replacng it with more inclusive, and hopefully more
> accurate, terminology.

I do not see what the problem is. And this just triggers a discussion
that is wasting time.

Please keep in mind that master/slave is something from very old times.
Quote "Slavery in ancient Rome played an important role in society and
the economy." Latin and Greek concepts are often used in science to
give words to things so that it's clear what we are talking about.

It is part of history, nobody can change that. The terms are generally
used in technology because people understand what they mean. Much like
male and female connectors.

--
How To Keep A Healthy Level Of Insanity:
6. In the memo field of all your checks, write "for sexual favors".

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

[Mike Fulton]

Hi

I would make a small change to say it is the 'current terminology' but not the 'proper terminology'. I understand there is work involved in making these changes to be more inclusive and that it isn't 'free'.

Does anyone else have thoughts on this change?

Thanks, Mike

--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to a topic in the Google Groups "vim_dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vim_dev/XG5whXSmJWk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAON-T_jJ40R1f2ge7Dm0FCKyNFGDx9_2wa7zYeFBcZUOm1BdBw%40mail.gmail.com.

[Bram Moolenaar]

> I would make a small change to say it is the 'current terminology' but not
> the 'proper terminology'. I understand there is work involved in making
> these changes to be more inclusive and that it isn't 'free'.
> Does anyone else have thoughts on this change?

I do not see any relation between the terms master and slave and "more
inclusive". This is using a catchprhase in the wrong context.

--
How To Keep A Healthy Level Of Insanity:

18. When leaving the zoo, start running towards the parking lot,
yelling "run for your lives, they're loose!!"

[Thomas Köhler]

Hi,

On Thu, Sep 08, 2022 at 06:37:24AM -0700, Mike Fulton <mikefulto...@gmail.com> wrote:
> Hi
>
> I would make a small change to say it is the 'current terminology' but not
> the 'proper terminology'. I understand there is work involved in making
> these changes to be more inclusive and that it isn't 'free'.
> Does anyone else have thoughts on this change?

I have never seen the point in any of these "inclusive" terms.
Replacing fitting terms everybody can easily understand with
something else which then is named differently in all projects
doesn't make the project more inclusive, instead it makes all
projects more inaccessible as it requires much more information
on what terminology (that once was crystal clear) now is supposed
to be used and what given terminology in a given project is
supposed to mean. But that seems to be the new normal in today's
hypersensitive world.

> Thanks, Mike

Ciao,
Thomas

--
Thomas Köhler Email: jean...@picard.franken.de
<>< WWW: http://gott-gehabt.de
IRC: tkoehler Freenode: thkoehler
PGP public key available from Homepage!