couldbethis / nano-configs Goto Github PK

first block:

• 4-6: perfect (showing that terminal color scheme can get in the way of seeing everything though)
• 7-8: colors not displaying?
• 9: same syntax as 7-8 but colors are working
• 10: same colors as 7-8 but perfect

second block:
-12-16: all perfect

third block:

• 18-23: OK I guess; nothing wrong but not very fun

fourth block:

• 25-28: perfect

The culprit appears to be nanorc.nanorc#L178 as commenting it out results in normal behaviour. I am not sure what the intended effect of this line is.

This is as of this commit: CouldBeThis/nanorc-syntax@80c809c

this bash script ekalinin/github-markdown-toc works well locally and might be perfect to learn how to use github actions.

disable the creation of so much backup files if this is included in the action.

trialed locally in 4ff1d41 and bdbc4f1

From README.md: todo: In the nanorc and .nanorc files

• Tidy up, remove old commented out configs
  • Perhaps organize old configs into alternative "sets" of command keys, color shemes
  • Perhaps split up files and include them in pieces Not possible! Turns out it is only possible to include syntaxfile whose contents are more limited than the nanorc. See the nanorc documentation.

from README:

• Organize files so it's clear what belongs to be and what belongs to the scopatz/nanorc repo
  • Perhaps include as a (forked) submodule
• Move this list to github issues?
• Move syntax changes that are just for myself to using extendsyntax and keep the main files general-purpose

In nanorc, the syntax highlighting files were originally linked as absolute paths from ~, such as

include "~/.nano/apacheconf.nanorc"

however to make things more organized and allow correct forking from original repo, I moved them into a separate subdirectory and changed to relative paths:

include "nano-syntax/apacheconf.nanorc"

it turns out that the path is relative to the current working directory from which you open nano. so the above will only work if you are in, for example, ~/.config/nano if that's the parent directory. It doesn't matter where the file you open is located, only where the user is.

Therefor I find it necessary to specify the full path like this as it is the only way to make it work:

include "~/.config/nano/nano-syntax/apacheconf.nanorc"

However, it does work to use a wildcard in specifying, so whereas previously each file had to be named specifically, in this way it is possible to catch every .nanorc file in the directory:

include "~/.config/nano/nanorc-syntax/*.nanorc"

Omitting the file extension results in errors as nano attempts to parse the other git related files.

See #6 where I investigated and found at nanorc.nanorc#L178 formatting applied to

The settings for errorcolor functioncolor keycolor numbercolor selectedcolor statuscolor stripecolor titlecolor are hardcoded but I should need to check if this should be changed/expanded/updated.

And I have to investigate if the file is up to date.

TODO: articulate this better.

I do not believe any of the information on the README is exactly correct at this instant.

from the README.md:

• Install instructions
  • Install script ???

In the file nanorc.nanorc, the comma confuses the regex

foreground:

icolor slate " slate"

background code:

icolor ,sea ",sea"

(linked blob does not have these colors yet, working in branch)

icolor ,bold ",bold"
icolor ,italic ",italic"

these do not work; produce error:

Color "italic" not understood

somewhat implied by nanorc man page - nano - File Formats | ManKier

The color pair may be preceded by bold and/or italic (separated by commas) to get a bold and/or slanting typeface, if your terminal can do those.

from README:

Improvements

• Markdown
  • add ==text== for highlighting
  • codeblocks are a bit odd; see if I misunderstand their use of if they need tweaking
  • add nicer (lower contrast) colors if code is in a link
  • improve anchor link display (higher constrast), e.g. [top](#top)
  • escape charecters
  • YAML frontmatter

Wishlist

• Optimize keyboard shortcuts for markdown
  • ctrl + 1 (and so on): add # to start of line (make heading level 1)
  • add new list item at same indentation as current.
    • if possible to detect whether currently in a list and what level, this should be automatic behaviour on enter
    • if not, assign to some other keystroke
    • also include for task list ( * [ ] or - [ ])
    • recognize either * or - lists
  • make current selection, or if none selected, current word bold, italic, strikethrough, ==highlighted==, code
  • insert link/image
    • with clipboard URL inserted and cursor in description/alt portion
    • if text selected, consider that text as description/alt and paste URL from clipboard
    • is it possible to detect if clipboard contains URL?
    • how to interact between various clipboards?
  • Extra help screen for shortcuts and/or markdown syntaxt cheatsheet
  • Generate a TOC

modifiers all wrong, most things in accessible and conflicts

will it be possible to create 1 file that works cross platform?

From the README.md:

• Spellchecking
• Make use of more keys I don't have on this particular device such as del, pg up/pg dn and function keys.
• Improve ctrl + arrow key navigation in how it deals with punctuation and special charecters... currently sort of confusing.
• Change contents of the help menu at the bottom

Could be useful (from [nanorc(5)](https://github.com/CouldBeThis/nano-configs/issues/%5BNANORC%5D(https://nano-editor.org/dist/latest/nanorc.5.html)):

• formatter - formatter program [argument ...]

  Invokes a full-buffer-processing program (if the active syntax defines one).

• execute

  Prompts for a program to execute. The program’s output will be inserted into the current buffer (or into a new buffer when M−F is toggled).

• macros:

  recordmacro

  Starts the recording of keystrokes -- the keystrokes are stored as a macro. When already recording, the recording is stopped.

  runmacro

  Replays the keystrokes of the last recorded macro.

See also #19

some settings do not properly highlight; maybe it's not been updated.

I am not sure what is the best way to go about this.

From the README.md:

• Summarize shortcuts (cheatsheet)
  • Perhaps including rationalization fos some decisions
• Improved (less confusing) interaction bewteen terminal emulator and nano

from README.md:

• Improve color scheme

Add or make nicer/more consistent the color scheme