You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after installing geeknote (as described on github) on a MacBook OS X 10.11.6 I get the following error whenever a note is edited.
Does anybody has the same problem and can point me to a solution?
Thanks!
Creation works nicely: $ geeknote create --title "geeknote" --content "best. evernote. client. ever." Note has been successfully created.
Edit works as well, but has a lot of error messages going with it:
$ geeknote edit --note "geeknote" --content "WRITE"
>> : Connect to Evernote.../Library/Python/2.7/site-packages/beautifulsoup4-4.5.1-py2.7.egg/bs4/__init__.py:181: UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("lxml"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.
The code that caused this warning is on line 9 of the file /usr/local/bin/geeknote. To get rid of this warning, change code that looks like this:
BeautifulSoup([your markup])
to this:
BeautifulSoup([your markup], "lxml")
Note has been successfully saved.
Should I really edit the source of geeknote? No problem, but I assume updates would break this again...
The text was updated successfully, but these errors were encountered:
Hello,
after installing geeknote (as described on github) on a MacBook OS X 10.11.6 I get the following error whenever a note is edited.
Does anybody has the same problem and can point me to a solution?
Thanks!
Creation works nicely:
$ geeknote create --title "geeknote" --content "best. evernote. client. ever."
Note has been successfully created.
Edit works as well, but has a lot of error messages going with it:
Should I really edit the source of geeknote? No problem, but I assume updates would break this again...
The text was updated successfully, but these errors were encountered: