Activity for John J. Jordan
-
John J. Jordan committed [0ce72f]
New URLs.
-
Fix URL in msi manifest.
-
Added tag windows-4.6 for changeset 1e3cda55fa98
-
I'd also suggest you consider 3.8, if you're unhappy with the 4.x series for whatever reason. There were no new features and many bugfixes in that release.
-
Unfortunately, that :include won't do what you want. The config file is segmented into parts, and --highlight has to appear in the first section -- it won't get interpreted properly in the last. I suggest you copy the joerc to your home directory and modify it from there (yes, we know -- this is the source of a lot of user complaints). That said, you could also just move it above the :include.
-
Further, I'm not exactly sure what the issue you're having with paste is. It would be helpful if you could illustrate with an example. If it is, as you referenced on another thread, an issue with indentation, that should have been fixed in 4.0 with bracketed paste. It would have required some changes to your config -- search the latest config for brpaste to see the relevant lines. Note that the terminal emulator must also support this feature. Otherwise, pre-4.0 I used to turn off autoindent ^T I...
-
The option you're looking for is highlight. Specifying --highlight either in joerc or on the command line ought to flip it off globally.
-
I tried to sort this out a couple of years ago when we merged in highlighter syntaxes from several contributors. The intended license grant is GPLv2+, though it was previously (imo, miscategorized as) 1+. I suppose we missed these and did not properly mark the remaining source files.
-
I guess one more data point I should ask for is whether you have -guess_utf8, -guess_non_utf8 or neither set in your config?
-
I may be able to take a closer look (repro, etc) at some point, but if you want to have a try then take a look here
-
Version 4.6
-
Merge from default
-
Merge from coroutine
-
Fix installer build on older VS/Wix versions.
-
Fixes to build on VS 2017.
-
Copyright dates
-
Script to clean up source directory for ZIP.
-
Version number
-
News
-
Merge ftyperc
-
Merge from coroutine
-
Missed merge
-
Merge from default.
-
Silly mistake
-
Fix cygwin build
-
#ifdef away non-POSIX stuff that breaks builds on some systems
-
Merge default to test_cases
-
Fix tests for FreeBSD, fix a test resulting from changing ansi->xterm
-
Display banner indicating whether a windows release exists, or what the next version that has it is. Actually reload versions.yml when it is changed from gulp dev.
-
Your branching strategy makes more sense. And yeah, the sh.jsf fix was on my mind here. I also broke a couple of things in the windows release (doesn't pick up user colors files, write access detection broke). Things like that.
-
Perhaps Mr. Super Packager joy/shallot could provide some perspective on the last point.
-
Release process - feature/bugfix releases
-
There are only 4 free bits (not enough to fully support the above) in the attr mask at present, including the MSB which would include code changes. That's going to be an obstacle in implementing all these fancy features the terminals keep adding. I guess everybody else just uses structs anymore anyway, but manipulating masks was so much nicer. I'd also note that the color scheme parser should probably silently ignore -colors it does not understand (it just generates an error today but doesn't fail),...
-
Jade is probably more in-line with current practices. Mustache is trendier (without venturing into the react-like stuff), but would have been a PITA here. Instead, I wanted something quick and dirty and EJS seemed to be the right fit. Node developers really are spoiled for choice, and there always seems to be at least half a dozen alternatives. It's nice but difficult to navigate sometimes. Anyway, I added it as a separate repo here (Website in the title bar) and uploaded to the project site with...
-
Add browser-sync development target
-
Add navbar
-
Add changelog to release pages
-
Initial commit
-
Second commit
-
Move from bower to npm, fix a ton of stuff, add history
-
Fix content padding
-
Fill out site a little more
-
Some inject stuff (to be removed)
-
Improve release pages
-
Don't use md for index+history
-
Touch up releases page
-
Add windows tips
-
Fill in some tasks
-
Add images, favicon
-
Fix typo in navbar
-
Start towards node-8 compatibility
-
Add tocbot for responsive sidebar toc in manual
-
Template work
-
Base 4.5 docs on slightly newer version to fix badly formatted NEWS
-
Fix Node 8
-
Tweak publish
-
Add readme
-
Make all images fluid
-
Add publish script
-
Reorder nav bar
-
Add installation instructions, tweak release page
-
Update readme, comments
-
improve the link rewriter
-
Fix anchors. Refactor some, use tocbot for hacking guide. Prevent nav dropdowns from interfering with toc, prevent anchors from interfering with buttons in release pages.
-
I followed through on this threat -- here's a repository that builds a static site, mostly from markdown in the source tree plus a little bit of metadata. It's git but there's no reason it has to be. Either way I can add it as a repo here and put it up if it's something you're ok with.
-
I followed through on this threat -- here's a repository that builds a static site, mostly from markdown in the source tree plus a little bit of metadata.
-
This is on a cloud VM with 2 dedicated cores of an E5-2673 v3 @ 2.40GHz. Not the highest IPS (and do mind the profiler tax), but this is even noticeable on my 4- and 6-series i7's. And no, it's far from the worst perf problem I've ever seen. Yes, I suppose I should have broken out startup/load profiles. The odd bit is that html doesn't use any character classes in its definition. Just the usual A-Za-z0-9, though more often than the other syntaxes (by a little bit). Perhaps all that's needed to solve...
-
html syntax slow to load
-
Is this not related to [#363]?
-
Is this not related to #363?
-
There's also this one: https://github.com/jjjordan/base16-joe If you find a vim scheme that you like (from vimcolors.com or the elsewhere) I can probably port it pretty easily -- just log an issue on github.com/jjjordan/joe-colors
-
There's also this one: https://github.com/jjjordan/base16-joe If you find a vim scheme that you like (from vimcolors.com or the elsewhere) I can probably port it pretty easily.
-
https://github.com/jjjordan/joe-colors/tree/master/output There are a few light schemes there, specifically moria-light and pyte. There are also some blue schemes if your terminal supports it.
-
NEWS
-
Add -highlighter_context to ftypes where syntaxes were updated to use it
-
Where did you find the documentation you quoted in the bug? I only see this: \* This finds zero or more of the item to the left. For example, if you give AB\*C as the search text, JOE will try to find an A followed by any number of Bs, and then a C. which is correct. This is from the user manual as well as the manpage. The syntax is a tradeoff with a separate find/replace mode. The rule is simple: escape meta-characters to use them as meta-characters rather than literal characters -- it's the exact...
-
. matches any one character, and then * specifies repetition of 0..many. The net effect is .* specifies "0 or more of any character". Back to your example, note that \0 is short for the NULL character, and NULLs are displayed as an underlined @ in JOE, which explains why it displays as it does. Capture groups start at \1, but first you need to specify a capture group with \( and \). To address your example: Search for The \(\.\*\) dog Replace with THE \1 DOG There's also a shortcut that I wasn't...
-
. matches any one character, and then * specifies repetition of 0..many. The net effect is .* specifies "0 or more of any character". Back to your example, note that \0 is short for the NULL character, and NULLs are displayed as an underlined @ in JOE, which explains why it displays as it does. Capture groups start at \1, but first you need to specify a capture group with \( and \). To address your example: Search for the \(\.\*\) dog Replace with the "\1" dog HTH -john
-
The regex engine was changed in 4.1 -- still with the funky-not-quite-standard syntax. To achieve what you want, you'd need to use the the\.\*dog in your first example, and A\.\*B in your second. Perhaps the documentation is not quite clear, but the contextual help is OK in my opinion: \* match 0 or more occurrences \. match any single char
-
Clean up access.
-
joe-editor.sourceforge.net woefully out of date
-
Fix access() glue function to actually check ACL's.
-
Check correct home directory for colors.
-
json.jsf marks valid number parts as error.
-
joe leaves the last column out
-
These were mostly fixed around the 3.8-4.0 timeframe. Reopen if that's not the case.
-
hex mode and utf-8
-
Convert all documentation to markdown
-
joe segfaults in help screen under certain circumstances
-
4.1 jmacs missing bindings and arrors under Cygwin mintty
-
Virus alarm in joewinpty.exe
-
Unknown option '--'
-
jmacs conflict for ^X ^F
-
Segmentation fault on 4.3
-
php syntax highlighting of variables fails in string constants
-
joe should consider Unicode private use area to be printable
-
Crash with 4.3 editing a perl file
-
Character class regex in UTF-8 mode reads uninitialized memory
-
Scrolling doesn't work with open options menu
-
Line numbers area too wide