witchard / mog Goto Github PK

Hi!

With this config in my ~/.mogrc;

[xml]
name=.*(?=(nuget\.config|NuGet\.Config|\.([fc]sproj|ruleset)))
argreplace=pygmentize -l xml -O style=solarized-light %F

I get the following output for files named like the following

• <folder path>/nuget.config
• and <folder path>/NuGet.Config
  (Don't ask my why the mix of capitalization, blame dotnet core on Linux =/).

All the while, this file matches nicely and displays correctly; <folder path>/<Project name>.csproj.

This is the error I get;

-> $ mog <failing Nuget xml file>
==> <failing Nuget xml file> <==
==> Error: "TypeError('replace() argument 2 must be str, not None',)" when processing file <failing Nuget xml file> <==

Add support for recursion into directories to run on the files inside them

Use a python tool instead maybe? Then it can be installed automatically when we do #7.

Ability to only recurse so far

Explain what things are being tried as it runs

Command line option for providing a different config

Add a config option / command line arg to force all output to go into less.

Show in the printed file name header which config section matched.

E.g. to capture script type for syntax highlighting

Matching on file --mime gives a more predictable output format.

Just a heads up I created a aur package for mog-git.

https://aur.archlinux.org/packages/mog-git/

If no rc file is found, install the example default.

Test on and fix any bugs when running on macOS

Document what file types are supported with the default config

With recursive and followsymlink on its possible to try and process broken symlinks which doesn't work.

-h is a bit vague as it references config variables. make it clearer

Use pygmentize -N to see if pygments can do highlighting for us.

When a BASH script('.sh' file) that has a decimal number in its contents is rendered with the mog command, it tends to produce erroneous output where the mantissa part(numbers after the decimal point) of the number is a different number in itself and not as a whole with the abscissa.

Here is a link for the output.

Currently we dont do anything!

This will allow a quick mog-ified overview.

Via setup.py and then a shield.

By default symlinks are reported as such by file, with the default config this can lead to symlinks being run through ls due to them not matching on higher level things. Following them in the python will mean this doesn't happen. Note, we probably also want to lower the priority of the filesystem section in the default config.

Simplify the install...

Hi,

If at any point you have some time, I think it would be very nice to automatically view formatted files like tables with something like column -xt or so