cvigilv / mateo.nvim Goto Github PK
View Code? Open in Web Editor NEWPersonal scientific-computing-oriented Neovim configuration
Personal scientific-computing-oriented Neovim configuration
Refer to link
I have saved a lot of Reddit posts with Neovim related things. This issue intends in
adding some of the useful things to my current setup.
So, life is changing and I need a reliable tool for the next couple of years that doesn't consume my time tinkering. It's time to make Neovim my sharp axe, therefore I have decided to aim this config into its "1.0" version and stop having it as a "rolling-release" kind of thingy.
This config must be ergonomic for doing science, don't forget about that!
v1.0 of my nvim setup should be focused on building a config that provides the following:
*.toml
)image.nvim
nvim-luapad
)]<key>
/[<key>
keymapsafter
, plugin
, ftplugin
, etc.Since I started working in Protera, the need for proper Python development tools integration
is required in order to make my life easier. This issue intends to setup all the required
tooling properly so I can proceed to enjoy the goodies and forget of the common problems.
Tools needed:
Most are already partially solved, but the plan is to have a robust setup that I can rely on
and forget. It would be good to use the guidelines proposed by Protera related to this tools
and make my setup reactive to pyproject.py
files.
On the spirit of starting my blog and improving my config, this issue aims to
provide a checklist of the things I intend to modify for my base UI (later on I
want to add more things using Hydra and other plugins).
The list goes as follows:
This are some starting points, maybe along the way I come up with more UI
elements I could modify.
Base structure in Okcolors
This file should contain tables and configurations for common things I use in my config,
e.g. borders for Telescope or other things
Stopped using MiniStarter
for oil.nvim
+ telescope.nvim
, but want to go back to using the
first. This issue intends in changing my current MiniStarter
config.
require("lazy").stats().startuptime
The modifications I commonly do to the colorschemes are also applied to other stuff, e.g.
oil.nvim or statusline. This issue plans to extract this behaviour and have it as a standalone
file in order to improve reliability of this.
Check this neovim/neovim#27339
Tasks:
Tasks
The currently implemented statusline works like a charm. It has the information I need, its
reactive for the different type of proyects I'm working on, etc. It has only 1 problem:
It has too much stuff!
This issue aims to solve this problema and streamline my statusline a little bit in order to
show only the completely relevant information depending on the proyect.
Some examples of the problems I have encountered:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.