edrx/eev

request for LICENSE file in root directory

Closed this issue · 8 comments

hwpplayer1 commented

Thanks for your hacking!

I think that it should be nice to make a LICENSE file in the root directory

See you

edrx commented

Thanks!!!
I am trying to follow the conventions in ELPA, and the git repository for eev is just one of the "externals" for ELPA... check:

# http://git.sv.gnu.org/r/emacs/elpa.git
# (find-git-links "http://git.sv.gnu.org/r/emacs/elpa.git")
# (find-git-links "http://git.sv.gnu.org/r/emacs/elpa.git" "elpagit")
# (find-efunction 'find-git-links)

� (eepitch-shell)
� (eepitch-kill)
� (eepitch-shell)
# rm -Rfv ~/usrc/elpa/
cd      ~/usrc/
git clone http://git.sv.gnu.org/r/emacs/elpa.git
cd      ~/usrc/elpa/

export PAGER=cat
git branch --list -a
git for-each-ref
git log --oneline --graph --all -20

# (find-fline "~/usrc/")
# (find-fline "~/usrc/elpa/")
# (find-gitk  "~/usrc/elpa/")

# (code-c-d "elpagit" "~/usrc/elpa/")
# (find-elpagitfile "")
# (find-elpagitfile "packages/")
# (find-elpagitfile "COPYING" "GNU GENERAL PUBLIC LICENSE" "Version 3")
# (find-elpagitfile "copyright_exceptions")
# (find-elpagitfile "externals-list")
# (find-elpagitfile "externals-list" "eev")

# (find-elpagitsh "find .* * | sort")
  • ❤️1
hwpplayer1 commented

@edrx Dear Eduardo, as i understand you follow conventions in ELPA, but i generally make a repository on my own git instance(now Gitea) and here on GitHub and others GitLab and Sourcehut, so the first thing for me to write a README and License file. Then for each file i just copy the customized license text within GNU Emacs or another IDE or Code Editor(VS Code Qt Creator etc.).

But this is your effort and i can not force you to do something like me. But i am sure that you want to contribute to people and who wants to run useful stuff.

Thanks again, hope we can move further for a better software. If you like a can start a translation effort for you, and software documentation.

See you

edrx commented

Hi @hwpplayer1,

More documentation would be great, especially if it is written as e-scripts, i.e., with text and executable notes interspersed, as I did in the eev tutorials and in the eev source code... there are very few examples of these things in the web written by people who were not me - see the slide "Prehistory 7" in my EmacsConf presentation in http://angg.twu.net/emacsconf2019.html.

I know far less git than I should - my notes on git are in http://angg.twu.net/e/git.e.html, but I am totally NON-fluent in it. Do you use magit? Can we help me with it? Would you like to chat about these ideas? See: http://angg.twu.net/contact.html

  • 👍1
edrx commented

Hi @hwpplayer1,
can you help me with this? My incomplete notes are here:
http://angg.twu.net/e/git.e.html#test-2020oct04

In the manpage of gitrevisions there is a figure (by Jon Loeliger) of a git repository with several branches and one merge... I am trying to build a repository like that, for tests...
Thanks in advance!!!

  • 👍1
edrx commented

Hi @hwpplayer1!
Take a look at this:
http://angg.twu.net/eev-intros/find-git-intro.html
Any help would be welcome!

  • 👍1
hwpplayer1 commented

Hi @hwpplayer1!
Take a look at this:
http://angg.twu.net/eev-intros/find-git-intro.html
Any help would be welcome!

I guess it will be fine, if i translate it to Turkish(Türkçe) Thanks, see you, but for a better and better solution :

Please

  1. Make a Project here, add/link repsoitory(repositories)
  2. Make a Roadmap as you like

Then i'll discuss for commits.

Happy Hacking!

edrx commented

Are "making a project", "adding repositories", and "making a roadmap" things that can be done locally for tests, i.e., using two git repositories, one in /tmp/git-test/repo1/ and another in /tmp/git-test/repo2/? Can you send me an eepitch block that does that, and include find-man links to the relevant man pages and URLs to webpages that you think that are relevant?

edrx commented

Note: find-man has an open bug that I did not have time to fix yet... an example:

  (find-man "1 git-commit")
  (find-man "1 git-commit" "-m <msg>, --message=<msg>")

The second find-man link should run the

  (ee-goto-position "-m <msg>, --message=<msg>")

AFTER the man page gets completely rendered, but the mechanism that delays its execution until the rendering it done it currently broken, and the ee-goto-position runs too soon. A workaround for that is to run the

  (find-man "1 git-commit")

to render the manpage, then bury its buffer with M-K, then run this:

  (find-man "1 git-commit" "-m <msg>, --message=<msg>")