alajmo / pinto Goto Github PK

I spent quite awhile yesterday remaking my personal theme, which I then exported to test out. I got a .vim version and I also did something that downloaded it as just the name with no extension, didn't look at that file until today.

I come back today to continue editing, try to import, and it won't take either file. I see it wants a JSON, the file I saved yesterday had no extension so I opened it in TextEdit and it's just blank. Tried adding .json to it but that's no good obviously because it's empty.

Is there any way to salvage this? Import my .vim that I had exported yesterday? Or am I just screwed and I have to start over?

Hello Again,

So I've got a colorscheme for markdown that's working well - and shell , vim, html and yaml filetypes.

But when I load the vimwiki/vimwiki plugin all that syntax formatting disappears.

My gut feeling is that I need a "vimwiki" option in the "Pinto > settings > choose which keywords you want to use" setting. It feels like there's a whole long list of highlight groups that I should specify for something like vimwikimarkdownH1 etc.

Can you tell me how I should do this please?
kr

Hello,
I'm fairly new to vim: my main intentions are (a) to move from zim to vimwiki and (b) use vim instead of nano for bash scripts. Both of those need to be pleasing to the eye - for me at least.

I love how the custom colorscheme creator works - the way the syntax object gets highlighted when you to click on an element in the example file, preview pane is just masterful! Wherever you got that idea from - it's brilliant and I'm going to steal it one day! I'm not sure what your plans are with this but honestly I think that pinta should be pinned on every vim tutorial ever and given some sort of recommended status by the core vim team.

I thought I had a problem (I've left the original issue I started writing below) - turns out I don't.
I leave this for any who follow ... to get the colorscheme to work for the first time I had to quit then re-launch vim; for some reason entering :so .vimrc didn't work; it's as though reloading the vim config doesn't force vim to update the schemes available in .vim/colors.

The scheme I've downloaded is beautiful. Thank you!
Now I'm going to finish it then create another one that's similar in pattern and visual impact but distinctly different ... my goal is to use :autocmd InsertEnter * :colorscheme 1aaA1 and :autocmd InsertLeave * :colorscheme 1aaA2` to have visual cues for which mode I'm in - and hopefully stop typing text in insert mode and entering my commands into the bodytext of my work!.

One feature request/ suggestion: it would be great to be able to edit the example file.
Thanks again. I'll be happy as a kid in a sweetshop for the next few days.

bw
whyglobaleyes

My problem is that I can't figure out how to apply the trial colorscheme I've created ...

• downloaded the scheme as both 1aaA2.vim and the json (can upload it if that helps)
• moved the .vim to ~/.vim/colors
• (got frustrated so ...moved my vimrc and started with a blank one that has only one line = colorscheme 1aaA2
• in vim entered :so .vimrc ==> plain white un-formatted text for both [sh] and [markdown] filetypes
• tried doing :colo 1aaA2 but that didn't help
• sanity check: if I change the vimrc to colorscheme murphy or enter :colo murphy then those both work and I can switch around to different builtin colorschemes.

So what - basic, idiot error thing - have I done wrong please?
thanks in advance.
whyglobaleyes

First, this site is great! It's helped me remake my theme I've been used to using for years in other editors.

I noticed there doesn't seem to be a shDerefSimple keyword in the bash keyword list. It's in the example script, but unless I missed it I didn't see it in the keyword list.

This can be worked around by manually editing the keyword group FWIW.