Commit 6b8cf5a4-9f48-46e4-90b6-b4d755586a6f/upstream - no-littering-el

+22

-0

.github/PULL_REQUEST_TEMPLATE.md less more

	0	Please use a dedicated feature branch. This is why:
	1
	2	https://github.com/magit/magit/wiki/Dedicated-pull-request-branches
	3
	4	Please try to follow the conventions.
	5
	6	https://github.com/tarsius/no-littering#conventions
	7
	8	In the past the majority of contributors have ignored at least some of the conventions. Others did not fully understand them or had a good reason to depart from the conventions but did not explain why that is so. Unfortunately it is hard for me as the maintainer to tell whether a contributor did not invest enough time to get things right or just forgot to be explicit about their thought process. The result is that a pull request is actually more work for me than a simple "please theme PACKAGE from URL".
	9
	10	Going forward contributors are expected to follow the conventions more closely from the get-go and to be explicit about their thought process. Adding such statements to commit messages, would be helpful for example:
	11
	12	- This file is used to store an s-expression.
	13	- This file is used to store raw text.
	14	- This is the only configuration/data file of the package.
	15	- This package does/doesn't take care of creating the containing
	16	directory if necessary. (If the package does not do it, then you
	17	should also fix that and submit an upstream pull request.)
	18
	19	Also please link to the repository of the package that your pull request is theming.
	20
	21	Thanks!

+3

-0

.gitignore less more

	0	/*.elc
	1	/*-autoloads.el
	2	/.config.mk

+14

-16

LICENSE less more

0
1		GNU GENERAL PUBLIC LICENSE
2		Version 3, 29 June 2007
3
4		Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
	0	GNU GENERAL PUBLIC LICENSE
	1	Version 3, 29 June 2007
	2
	3	Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
5	4	Everyone is permitted to copy and distribute verbatim copies
6	5	of this license document, but changing it is not allowed.
7	6
8		Preamble
	7	Preamble
9	8
10	9	The GNU General Public License is a free, copyleft license for
11	10	software and other kinds of works.

68	67	The precise terms and conditions for copying, distribution and
69	68	modification follow.
70	69
71		TERMS AND CONDITIONS
	70	TERMS AND CONDITIONS
72	71
73	72	0. Definitions.
74	73

76	75
77	76	"Copyright" also means copyright-like laws that apply to other kinds of
78	77	works, such as semiconductor masks.
79
	78
80	79	"The Program" refers to any copyrightable work licensed under this
81	80	License. Each licensee is addressed as "you". "Licensees" and
82	81	"recipients" may be individuals or organizations.

509	508	covered work in a country, or your recipient's use of the covered work
510	509	in a country, would infringe one or more identifiable patents in that
511	510	country that you have reason to believe are valid.
512
	511
513	512	If, pursuant to or in connection with a single transaction or
514	513	arrangement, you convey, or propagate by procuring conveyance of, a
515	514	covered work, and grant a patent license to some of the parties

618	617	Program, unless a warranty or assumption of liability accompanies a
619	618	copy of the Program in return for a fee.
620	619
621		END OF TERMS AND CONDITIONS
622
623		How to Apply These Terms to Your New Programs
	620	END OF TERMS AND CONDITIONS
	621
	622	How to Apply These Terms to Your New Programs
624	623
625	624	If you develop a new program, and you want it to be of the greatest
626	625	possible use to the public, the best way to achieve this is to make it

645	644	GNU General Public License for more details.
646	645
647	646	You should have received a copy of the GNU General Public License
648		along with this program. If not, see <http://www.gnu.org/licenses/>.
	647	along with this program. If not, see <https://www.gnu.org/licenses/>.
649	648
650	649	Also add information on how to contact you by electronic and paper mail.
651	650

664	663	You should also get your employer (if you work as a programmer) or school,
665	664	if any, to sign a "copyright disclaimer" for the program, if necessary.
666	665	For more information on this, and how to apply and follow the GNU GPL, see
667		<http://www.gnu.org/licenses/>.
	666	<https://www.gnu.org/licenses/>.
668	667
669	668	The GNU General Public License does not permit incorporating your program
670	669	into proprietary programs. If your program is a subroutine library, you
671	670	may consider it more useful to permit linking proprietary applications with
672	671	the library. If this is what you want to do, use the GNU Lesser General
673	672	Public License instead of this License. But first, please read
674		<http://www.gnu.org/philosophy/why-not-lgpl.html>.
675
	673	<https://www.gnu.org/licenses/why-not-lgpl.html>.

+4

-2

README.md less more

11	11
12	12	This package sets out to fix this by changing the values of path
13	13	variables to put configuration files in `no-littering-etc-directory`
14		(defaulting to `~/.emacs.d/etc/`) and persistent data files in
15		`no-littering-var-directory` (defaulting to `~/.emacs.d/var/`), and
	14	(defaulting to "etc/" under `user-emacs-directory`, thus usually
	15	`"~/.emacs.d/etc/"`) and persistent data files in
	16	`no-littering-var-directory` (defaulting to `"var/"` under
	17	`user-emacs-directory`, thus usually `"~/.emacs.d/var/"`), and
16	18	by using descriptive file names and subdirectories when appropriate.
17	19	This is similar to a color-theme; a "path-theme" if you will.
18	20

+11

-4

no-littering.el less more

0	0	;;; no-littering.el --- help keeping ~/.emacs.d clean -- lexical-binding: t; --
1	1
2		;; Copyright (C) 2016-2020 Jonas Bernoulli
	2	;; Copyright (C) 2016-2021 Jonas Bernoulli
3	3
4	4	;; Author: Jonas Bernoulli <jonas@bernoul.li>
5	5	;; Homepage: https://github.com/emacscollective/no-littering

35	35
36	36	;; This package sets out to fix this by changing the values of path
37	37	;; variables to put configuration files in `no-littering-etc-directory'
38		;; (defaulting to "~/.emacs.d/etc/") and persistent data files in
39		;; `no-littering-var-directory' (defaulting to "~/.emacs.d/var/"), and
	38	;; (defaulting to "etc/" under `user-emacs-directory', thus usually
	39	;; "~/.emacs.d/etc/") and persistent data files in
	40	;; `no-littering-var-directory' (defaulting to "var/" under
	41	;; `user-emacs-directory', thus usually "~/.emacs.d/var/"), and
40	42	;; by using descriptive file names and subdirectories when appropriate.
41	43	;; This is similar to a color-theme; a "path-theme" if you will.
42	44

286	288	(setq bmkp-current-bookmark-file (var "bmkp/current-bookmark.el"))
287	289	(setq bmkp-last-bookmark-file (var "bmkp/last-bookmark.el"))
288	290	(setq bookiez-file (var "bookiez"))
	291	(setq cider-repl-history-file (var "cider-repl-history.el"))
	292	(eval-after-load 'command-log-mode
	293	`(make-directory ,(var "command-log-mode-logging/") t))
	294	(setq clm/logging-dir (var "command-log-mode/logging/"))
289	295	(eval-after-load 'company
290	296	`(make-directory ,(var "company/") t))
291		(setq cider-repl-history-file (var "cider-repl-history.el"))
292	297	(setq company-statistics-file (var "company/statistics.el"))
293	298	(setq company-tabnine-binaries-folder (var "company/tabnine-binaries"))
294	299	(setq dap-breakpoints-file (var "dap/breakpoints.el"))

352	357	(eval-after-load 'lookup
353	358	`(make-directory ,(etc "lookup/") t))
354	359	(setq lookup-init-directory (etc "lookup/"))
	360	(setq lsp-eslint-library-choices-file (var "lsp/eslint-library-choices.el"))
355	361	(setq lsp-python-ms-dir (var "lsp-python-ms/"))
356	362	(eval-after-load 'lsp-mode
357	363	`(make-directory ,(var "lsp/") t))

379	385	(setq org-journal-cache-file (var "org/journal-cache.el"))
380	386	(setq org-recent-headings-save-file (var "org/recent-headings.el"))
381	387	(setq org-registry-file (var "org/registry.el"))
	388	(setq org-roam-db-location (var "org/org-roam.db"))
382	389	(setq package-quickstart-file (var "package-quickstart.el"))
383	390	(setq pandoc-data-dir (etc "pandoc-mode/"))
384	391	(setq pcache-directory (var "pcache/"))