Tested on Ubuntu 20, 21 earlier and they were not working. So upgraded Ubutbu to latest 22 version.
The issue is: The built in Kernals of Ubuntu and many Linux Kernals (between ) have the CH340 drivers broken / have bugs and not fixed (from kernal 5.4.0-87 and above)
Note: I didn't try on linux kernal 5.4.0-86 my self. I though I will see how is the situation in the latest linux kernal (as of 16/05/2022)
| <?xml version="1.0" encoding="UTF-8" ?> | |
| <!-- | |
| MINDMAPEXPORTFILTER org;orgmode Orgmode | |
| v. 0.1 | |
| This code released under the GPL. : (http://www.gnu.org/copyleft/gpl.html) | |
| Document : mm2orgmode.xsl |
| import threading | |
| from IPython.display import display | |
| import ipywidgets as widgets | |
| import time | |
| def get_ioloop(): | |
| import IPython, zmq | |
| ipython = IPython.get_ipython() | |
| if ipython and hasattr(ipython, 'kernel'): | |
| return zmq.eventloop.ioloop.IOLoop.instance() | |
| ioloop = get_ioloop() |
Here are the simple steps needed to create a deployment from your local GIT repository to a server based on this in-depth tutorial.
You are developing in a working-copy on your local machine, lets say on the master branch. Most of the time, people would push code to a remote server like github.com or gitlab.com and pull or export it to a production server. Or you use a service like deepl.io to act upon a Web-Hook that's triggered that service.
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)
| # Detect operating system in Makefile. | |
| # Author: He Tao | |
| # Date: 2015-05-30 | |
| OSFLAG := | |
| ifeq ($(OS),Windows_NT) | |
| OSFLAG += -D WIN32 | |
| ifeq ($(PROCESSOR_ARCHITECTURE),AMD64) | |
| OSFLAG += -D AMD64 | |
| endif |
| <!doctype html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title> | |
| {% if page.title %} | |
| {{ page.title }} | {{ site.title }} | |
| {% else %} | |
| {{ site.title }} |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
| <?xml version="1.0" encoding="UTF-8" ?> | |
| <!-- | |
| MINDMAPEXPORTFILTER md;markdown Markdown | |
| v. 0.1 | |
| This code released under the GPL. : (http://www.gnu.org/copyleft/gpl.html) | |
| Document : mm2markdown.xsl |
