New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated from your website, added package.el headers #1

Closed
wants to merge 2 commits into
base: master
from

Conversation

Projects
None yet
3 participants
@jpkotta

jpkotta commented Jun 2, 2012

I'm planning on submitting this to melpa (http://melpa.milkbox.net/), so I figured I'd get the latest version. I don't think the package.el headers are necessary for melpa, but they would be for something like elpa.

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Dec 31, 2012

Ping. Also please create a tag.

tarsius commented Dec 31, 2012

Ping. Also please create a tag.

@jpkotta

This comment has been minimized.

Show comment
Hide comment
@jpkotta

jpkotta Jan 2, 2013

I'm not sure why I should tag it, or what sort of tag to give it. Please clarify.

jpkotta commented Jan 2, 2013

I'm not sure why I should tag it, or what sort of tag to give it. Please clarify.

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Jan 3, 2013

What I mean is a git tag:

git tag 1.22  # or after merging the request probably 1.23
git push -t

Why? It's just nice knowing what version is installed (I use git
submodules) without having to look in the file. Not really that
important. The original pull request is more important, but since I
stumbled across and was going to remind you of it I thought I would
mention that too.

Also since this is stored in git now I would

+;; $Revision: 1.22 $
-;; Version: 1.22

And the .gitignore seems rather useless:

  • *.elc belongs in a global ignore file, and
  • the other files don't exist

By now that should probably be a separate github issue :-)

tarsius commented Jan 3, 2013

What I mean is a git tag:

git tag 1.22  # or after merging the request probably 1.23
git push -t

Why? It's just nice knowing what version is installed (I use git
submodules) without having to look in the file. Not really that
important. The original pull request is more important, but since I
stumbled across and was going to remind you of it I thought I would
mention that too.

Also since this is stored in git now I would

+;; $Revision: 1.22 $
-;; Version: 1.22

And the .gitignore seems rather useless:

  • *.elc belongs in a global ignore file, and
  • the other files don't exist

By now that should probably be a separate github issue :-)

@davep

This comment has been minimized.

Show comment
Hide comment
@davep

davep May 24, 2016

Owner

I'm ashamed to say I've only just noticed this. I'm just getting back into heavily using GNU emacs after a long period of being fairly inactive and, because of this, the whole package management thing is actually new to me. I'm going to be doing some reading up on what's involved and hope to tidy up all my code -- boquote.el included -- to better fit with how emacs is doing things these days.

Owner

davep commented May 24, 2016

I'm ashamed to say I've only just noticed this. I'm just getting back into heavily using GNU emacs after a long period of being fairly inactive and, because of this, the whole package management thing is actually new to me. I'm going to be doing some reading up on what's involved and hope to tidy up all my code -- boquote.el included -- to better fit with how emacs is doing things these days.

@davep

This comment has been minimized.

Show comment
Hide comment
@davep

davep Mar 22, 2017

Owner

Coming back to looking at package systems I was tinkering with boxquote and made similar changes before remembering this was here. So... thanks for doing this, sorry I made a conflicting change (still trying to figure everything out). Similar changes are being made so it was worth the effort.

Owner

davep commented Mar 22, 2017

Coming back to looking at package systems I was tinkering with boxquote and made similar changes before remembering this was here. So... thanks for doing this, sorry I made a conflicting change (still trying to figure everything out). Similar changes are being made so it was worth the effort.

@davep davep closed this Mar 22, 2017

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Mar 22, 2017

Thanks!

Coming back to looking at package systems

Since you are using the plural... By now I have released my own: borg ;-)

tarsius commented Mar 22, 2017

Thanks!

Coming back to looking at package systems

Since you are using the plural... By now I have released my own: borg ;-)

@davep

This comment has been minimized.

Show comment
Hide comment
@davep

davep Mar 22, 2017

Owner

Just when I'd managed to get the hang of one, almost..... ;)

I'll be sure to take a look. :)

Owner

davep commented Mar 22, 2017

Just when I'd managed to get the hang of one, almost..... ;)

I'll be sure to take a look. :)

@tarsius

This comment has been minimized.

Show comment
Hide comment
@tarsius

tarsius Mar 22, 2017

You should also check out use-package. It's not a package manager, but a tool to keep your configuration under control.

tarsius commented Mar 22, 2017

You should also check out use-package. It's not a package manager, but a tool to keep your configuration under control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment