Skip to content

Tags: jsoncomma/sublime-jsoncomma

Tags

v0.2.8

Toggle v0.2.8's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request #18 from joreiff/joreiff-issue-17

Fix plugin being stuck in downloading state

fix #17

v0.2.7

Toggle v0.2.7's commit message
server: less verbosity on normal flow

only print debug error if there is an unexpected error when starting the
server (we expect an error when opening the socket, ie. the port is
already used).

v0.2.6

Toggle v0.2.6's commit message
server: force use of IPv4 for both client and server

Otherwise, it lags on Windows. ref #10

v0.2.5

Toggle v0.2.5's commit message
server: start server on save if it isn't running

v0.2.4

Toggle v0.2.4's commit message
server: idempotent style client

the client doesn't need to control the server process anymore. If there
is something running on 2442, it assumes it's the jsoncomma server. If
not, it starts it, and forgets about the process. The reason is that we
cannot reliably shutdown the process because sublime text doesn't have a
on_exit event

v0.2.3

Toggle v0.2.3's commit message
plugin: handle view.file_name() is None

fix #8

v0.2.2

Toggle v0.2.2's commit message
fix bug in server.download on mac os

fix #7

v0.2.1

Toggle v0.2.1's commit message
server: fix bug: always use cls instead of server

it use to be fine (cls is server use to be True), but I think that
moving server into it's own separate file breaks that equality, and so
attributes (like server.infos) were set on "cls" (server.server), and
refer to as server (json_comma.server), which obviously didn't work. I'm
not 100% confident (pretty certain there's something I'm not getting
right about this), but it works now, and it's late

v0.2.0

Toggle v0.2.0's commit message
server: improve confirmation box dialog

I still don't really like it though...

v0.1.4

Toggle v0.1.4's commit message
fix README.md#installation