Sponsored Content
The Lounge What is on Your Mind? New Code Tags (Syntax Highlighting) Post 303019503 by Neo on Saturday 30th of June 2018 10:03:16 PM
Old 06-30-2018
Yes. Our existing GeSHi syntax highlighter works OK and it is a server side process. SyntaxHighligher is client-side JavaScript process and so it is therefore kinda' slow to load; and since it does not solve the scrollbar issue and does not do a great job of actual syntax highlighting, I think better to table this and stick with our generic code tags and let people use GeSHi highlighting if they want.

I will put it on my TODO list to upgrade GeSHi to the latest version and add the AWK syntax highlighting code. Maybe I will create a few buttons in the editor for highlighting.
This User Gave Thanks to Neo For This Post:
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Emacs color syntax highlighting

So... i cant get it to work. I had already posted this but it got deleted. Details: Im running SSH shell on Windows XP, connecting to a server whose term is vt100 (someone asked me that last time) Im trying to get the syntax highlighting in cc mode to work in color, but its black and... (0 Replies)
Discussion started by: viejid
0 Replies

2. UNIX for Dummies Questions & Answers

color highlighting with 'more','grep' and 'vi'

Hi all, i would to find out how can i turn on color hightlighting with the 'more' command. When i view a big file, i tend to use the 'more' command and i would search for a interested string with the '/' command. Something the search returns more than 1 line found on the screen, how can i... (0 Replies)
Discussion started by: new2ss
0 Replies

3. Programming

Vim highlighting annoyance

I was using vim about an hour ago doing abit of python (i only just started using vim). And I think i typed something wrong, and all of a sudden the letter i is always highlighted. Turning syntax off and on didn't work. and i couldent find the solution online. Thanks in advanced. (1 Reply)
Discussion started by: vimhelp
1 Replies

4. UNIX and Linux Applications

gedit/gtksourceview: Updating types for syntax highlighting?

I wrote a new .lang file for syntax highlighting a language I use frequently. It works fine, except that it doesn't glob onto the files automatically. Is there a utility I need to run to update a gtksourceview database? Here's the relevant portion of the code. <language id="pari"... (0 Replies)
Discussion started by: CRGreathouse
0 Replies

5. Shell Programming and Scripting

How to stop Vim from highlighting lines 73+

I am slowly developing my .vimrc and would like to know how to turn off the highlighting (black text on orange background) which starts at line 73. This doesn't seem to be controlled by any selected/customized colorscheme. I do CFD, and some older codes I use are written in F77, for which this... (2 Replies)
Discussion started by: drbones
2 Replies

6. AIX

[Vim] Question about syntax highlighting

Hi all, my sysadmin installed Vim packages (vim-enhanced-6.3-1 & vim-common-6.3-1) on an Aix system (7.1.0.0). I log in using Putty (vs 0.54) and got an annoying underline issue. All strings and var names are underlined as you can see on the attached file Is it possible to get rid of that... (4 Replies)
Discussion started by: Fundix
4 Replies

7. UNIX for Dummies Questions & Answers

Reapplying syntax highlighting in vim

I had a bash script (ma_report.sh) that I was editing when my VPN connection died. So, when I reconnected, I recovered my changes and reopened the file. Everything looks fine except that there is no longer any syntax highlighting. Using ':syntax on' does not work. Other bash scripts in vim do... (1 Reply)
Discussion started by: treesloth
1 Replies

8. Shell Programming and Scripting

Highlighting duplicate string on a line

Hi all I have a grep written to pull out values; below (in the code snip-it) is an example of the output. What I'm struggling to do, and looking for assistance on, is identifying the lines that have duplicate strings. For example 74859915K74859915K in the below is 74859915K repeated twice but... (8 Replies)
Discussion started by: brighty
8 Replies
LE(1)							      General Commands Manual							     LE(1)

NAME
le - full screen text editor SYNOPSIS
le [options] filename DESCRIPTION
le is a text editor which offers wide range of capabilities with a simple interface. It has a pull down menu and a simple help system to get started. See KEYS section below to learn about key combinations. Among its features there are: various operations with stream and rectangular blocks, search and replace with full regular expressions, text formatting, undelete/uninsert, hex editing, tunable key sequences, tunable colors, tunable syntax highlighting. The editor currently supports only one loaded file at a time. KEYS
Here are some starting hints: F10 or C-n menu F1 help C-x exit (cancel) Arrows navigate In the editor the following key description is used: Key1-Key2 simultaneous key1 and key2 press Key1+Key2 sequential keys press Key1 | Key2 press Key1 OR Key2 ^Key Ctrl-Key ~Key Shift-Key ^~Key Ctrl-Shift-Key | Alt-Key Some of ^Fx, ~Fx, ^~Fx can be typed as ESC+Fx. The rest of key combinations can be seen in help, in menu and in the keyboard map (default one can be seen with le --dump-keymap). There is support for block filtering through an external program, a command output read-in, writing a block through a command. To read or write block from/to a command, use F4+R or F4+W and file name of the following format: ``|command args''. Filtering is achieved by F4+| followed by command name. STATUS LINE
On the status line you can see current line, column, the size of loaded file, the code of character under cursor, several one letter flags, file name, offset in bytes from the file beginning and percent position in the file. One letters flags are: * - modified; R - Russian keyboard (works only on certain terminals); I - insert, O - overstrike; A - autoindent; D - dos style line terminators (CR NL); U - undelete possible, u - uninsert possible; B - column block mode. TEXT PROTECTION
To prevent changes loss on crash, le regularly dumps the editing text, if changed, to ~/.le/tmp/FILENAME.PID , where FILENAME is the file name with slashes converted to underlines; PID is the process id of the editor process. When the editor gets a fatal signal, it also dumps the text, to ~/.le/tmp/DUMP-SIG-FILENAME.PID , where SIG is the signal number. OPTIONS
-r, --read-only Work as viewer, don't allow changes. If your system supports mmap(2), it will be used to get file contents to memory. -h, --hex-mode Start in hex mode --mmap Use mmap(2) to load file read-only. Can be used to view very large files or even devices. This implies -h. --mmap-rw Use mmap(2) to load file read-write in MAP_SHARED mode. Use with caution -- the changes go directly to file or disk, no undo. In this mode only replace can be used, but it allows editing of very large files or even devices. This implies -h. -b, --black-white Start in black & white mode -c, --color Start in color mode --dump-keymap Dump default keymap to stdout and exit --dump-colors Dump default color map to stdout and exit --version Print the version of LE and exit --help Print short description of options and exit FILES
DATADIR/colors ~/.le/colors DATADIR/colors-$TERM ~/.le/colors-$TERM Color palette description. Those files are sequentially read and color definitions in later files have higher precision. ~/.le/keymap-$TERM DATADIR/keymap-$TERM ~/.le/keymap DATADIR/keymap Key map descriptions. Only the first existing file is read. ~/.le/term-$TERM DATADIR/term-$TERM Terminal specific options. Only the first existing file is read. Use Options->Terminal menu to tune the options. ./.le.ini ~/.le/le.ini DATADIR/le.ini Options. Only the first existing file is read. Use menu Options to tune these. .le.syntax ~/.le/syntax DATADIR/syntax Syntax highlighting rules. Only the first existing file is read. There is no default built-in in the editor, so if those files are not present you won't see any syntax highlighting. ~/.le/mainmenu DATADIR/mainmenu Main editor menu. It has simple text format. Only the first existing file is read. ~/.le/history Various histories are saved here. Do not edit by hand. DATADIR is determined at compile time by configure script (pkgdatadir variable). By default it has value /usr/local/share/le. AUTHOR
The LE editor was written by Alexander V. Lukyanov <lav@yars.free.net>. 28 Sep 2000 LE(1)
All times are GMT -4. The time now is 02:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy