JuliaEditorSupport / Julia Emacs
Licence: other
Julia support in Emacs.
Stars: ✭ 187
Programming Languages
julia
2034 projects
Labels
Projects that are alternatives of or similar to Julia Emacs
Kubel
Emacs extension for controlling Kubernetes with limited permissions
Stars: ✭ 166 (-11.23%)
Mutual labels: emacs
Go Org
Org mode parser with html & pretty printed org rendering. also shitty static site generator.
Stars: ✭ 177 (-5.35%)
Mutual labels: emacs
Spacemacs Rocks
Happy Hacking Emacs & Spacemacs (Simplified Chinese)
Stars: ✭ 2,003 (+971.12%)
Mutual labels: emacs
Es Mode
An Emacs major mode for interacting with Elasticsearch
Stars: ✭ 176 (-5.88%)
Mutual labels: emacs
Nox
Nox is a lightweight, high-performance LSP client for Emacs
Stars: ✭ 181 (-3.21%)
Mutual labels: emacs
Emacs Eclim
This project brings some of the great eclipse features to emacs developers. It is based on the eclim project, which provides eclipse features for vim. Development from senny/emacs-eclim has moved here.
Stars: ✭ 166 (-11.23%)
Mutual labels: emacs
Elispcheatsheet
Quick reference to the core language of Emacs ---Editor MACroS.
Stars: ✭ 186 (-0.53%)
Mutual labels: emacs
Pomidor
Pomidor is a simple and cool pomodoro technique timer.
Stars: ✭ 183 (-2.14%)
Mutual labels: emacs
Emacs major mode for the julia programming language
Installation
Installing from MELPA
Unless you want to develop this package, it is recommended that you use it from MELPA:
-
Add
(require 'julia-mode)
to your Emacs init file.
Using the source repository directly
Clone this repository, then use
(add-to-list 'load-path "path-to-julia-mode")
(require 'julia-mode)
Contributing
Contributions are welcome, in the form of pull requests.
Please
-
add unit tests whenever possible. This may require that functions are broken up into an interface and a backend function, then you can test the backend one.
-
add a short summary in the Unreleased section of the CHANGELOG.
-
use the
rx
macro (S-expressions) whenever rewriting existing regular expressions or introducing new ones; it keeps the code much more readable.
We do our best to provide feedback within 2 weeks, feel free to bump in a comment after that.
Note that the project description data, including the texts, logos, images, and/or trademarks,
for each open source project belongs to its rightful owner.
If you wish to add or remove any projects, please contact us at [email protected].