[vim/vim] Directory Organization Changes (PR #12335)

13 views
Skip to first unread message

CadmusBashLog

unread,
May 3, 2023, 1:21:45 AM5/3/23
to vim/vim, Subscribed

Directory over time may provide a better user experience for those new to Vim or those returning users on an unfamiliar workstation. Changes may cause potential conflicts and should be addressed as such in the future. This change keeps things simple in places, rather than too simple in not enough places.
Changes to be committed:
deleted: README.txt
renamed: READMEdir/README_ami.txt -> README/Amiga/README_ami.txt
renamed: READMEdir/README_ami.txt.info -> README/Amiga/README_ami.txt.info
renamed: READMEdir/README_amibin.txt -> README/Amiga/README_amibin.txt
renamed: READMEdir/README_amibin.txt.info -> README/Amiga/README_amibin.txt.info
renamed: READMEdir/README_amisrc.txt -> README/Amiga/README_amisrc.txt
renamed: READMEdir/README_amisrc.txt.info -> README/Amiga/README_amisrc.txt.info
renamed: READMEdir/Contents.info -> README/Binary/Contents.info
renamed: READMEdir/README.txt.info -> README/Binary/README.txt.info
renamed: READMEdir/README_extra.txt -> README/Binary/README_extra.txt
renamed: READMEdir/Vim.info -> README/Binary/Vim.info
renamed: READMEdir/Xxd.info -> README/Binary/Xxd.info
renamed: READMEdir/runtime.info -> README/Binary/runtime.info
renamed: READMEdir/src.info -> README/Binary/src.info
renamed: READMEdir/vimdir.info -> README/Binary/vimdir.info
renamed: CONTRIBUTING.md -> README/CONTRIBUTING.md
renamed: READMEdir/Contents -> README/Contents
renamed: READMEdir/README_haiku.txt -> README/Haiku/README_haiku.txt
renamed: LICENSE -> README/LICENSE
renamed: READMEdir/README_bindos.txt -> README/MS/README_bindos.txt
renamed: READMEdir/README_dos.txt -> README/MS/README_dos.txt
renamed: READMEdir/README_ole.txt -> README/MS/README_ole.txt
renamed: READMEdir/README_vms.txt -> README/MS/README_vms.txt
renamed: READMEdir/README_w32s.txt -> README/MS/README_w32s.txt
renamed: READMEdir/README_mac.txt -> README/Macintosh/README_mac.txt
renamed: README.md -> README/README.md
renamed: README_VIM9.md -> README/README_VIM9.md
renamed: READMEdir/README_os2.txt -> README/UNIX/README_os2.txt
renamed: READMEdir/README_os390.txt -> README/UNIX/README_os390.txt
renamed: READMEdir/README_src.txt -> README/UNIX/README_src.txt
renamed: READMEdir/README_srcdos.txt -> README/UNIX/README_srcdos.txt
renamed: READMEdir/README_unix.txt -> README/UNIX/README_unix.txt
renamed: uninstall.txt -> README/uninstall.txt
renamed: .appveyor.yml -> install/.appveyor.yml
renamed: .cirrus.yml -> install/.cirrus.yml
renamed: .codecov.yml -> install/.codecov.yml
renamed: .coveralls.yml -> install/.coveralls.yml
renamed: Filelist -> install/Filelist
renamed: Makefile -> install/Makefile
renamed: configure -> install/configure
renamed: vimtutor.bat -> install/vimtutor.bat
renamed: vimtutor.com -> install/vimtutor.com


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/12335

Commit Summary

  • 8932c44 Format changes made for better directory organization. Having a more uniform

File Changes

(42 files)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/12335@github.com>

CadmusBashLog

unread,
May 3, 2023, 1:24:11 AM5/3/23
to vim/vim, Subscribed

Closed #12335.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/12335/issue_event/9151658775@github.com>

CadmusBashLog

unread,
May 3, 2023, 1:31:53 AM5/3/23
to vim/vim, Subscribed

Reopened #12335.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/12335/issue_event/9151686535@github.com>

CadmusBashLog

unread,
May 3, 2023, 3:25:20 AM5/3/23
to vim/vim, Subscribed

Closed #12335.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/12335/issue_event/9152319282@github.com>

Bram Moolenaar

unread,
May 3, 2023, 5:55:53 PM5/3/23
to vim/vim, Subscribed

Thanks for closing. Having a "README" directory causes problems in various places expecting a README file.
The CI config files must be in the root, AFAIK.
Other changes might be OK if the tools using them would also be changed. But is it an improvement?


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/12335/c1533803778@github.com>

CadmusBashLog

unread,
May 3, 2023, 7:52:56 PM5/3/23
to vim/vim, Subscribed

Thanks for closing. Having a "README" directory causes problems in various places expecting a README file. The CI config files must be in the root, AFAIK. Other changes might be OK if the tools using them would also be changed. But is it an improvement?

brammool Thank you for the clarity and guidance because I'll take this forward with other future software. Your response means more to me than you may know. The point I am understanding is that changes in general may be nice, but just because it is a change with some benefit, it does not mean that it is needed.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/12335/c1533891289@github.com>

Bram Moolenaar

unread,
May 4, 2023, 10:49:21 AM5/4/23
to vim/vim, Subscribed


> [brammool](https://github.com/brammool) Thank you for the clarity and

> guidance because I'll take this forward with other future software.
> Your response means more to me than you may know. The point I am
> understanding is that changes in general may be nice, but just because
> it is a change with some benefit, it does not mean that it is needed.

What I said was in the context of Vim, which has existed for many years
and targets a wide range of platforms. If you start a new project you
may choose a different layout, since you don't have to worry about what
users expect from previous versions.

A lot is personal preference though. I like just typing "make" to
build something. Others use more sophisticated tools, but that usually
requires reading the installation guide to figure out what dependencies
to install, what tools to run in what sequence, etc. For example, cmake
can be used instead of make. You get powerful features, but with that
comes complexity and a limited set of platforms that are supported.

--
The budget process was invented by an alien race of sadistic beings who
resemble large cats.
(Scott Adams - The Dilbert principle)

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


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/12335/c1534918135@github.com>

Reply all
Reply to author
Forward
0 new messages