Sponsored Content
The Lounge What is on Your Mind? New Code Tags (Syntax Highlighting) Post 303019478 by RudiC on Saturday 30th of June 2018 01:17:22 AM
Old 06-30-2018
While I still appreciate the line numbering, I found editing and formatting code snippets extremely tedious with the new approach, having to go to and fro many times more than before.
In retrospect, I'd vote for the original code tags.
This User Gave Thanks to RudiC 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
ctags(1)						      General Commands Manual							  ctags(1)

NAME
ctags - create a tags file SYNOPSIS
files ... DESCRIPTION
makes a tags file for ex(1) (or vi(1)) from the specified C, Pascal and FORTRAN sources. A tags file gives the locations of specified objects (for C, functions, macros with argments, and typedefs; Pascal, procedures, programs and functions; FORTRAN, subroutines, programs and functions) in a group of files. Each line of the tags file contains the object name, the file in which it is defined, and an address specification for the object definition. Output is sorted in ascending collation order (see Environment Variables below). All objects except C typedefs are searched with a pattern, typedefs with a line number. Specifiers are given in separate fields on the line, separated by spaces or tabs. Using the tags file, can quickly find these objects' definitions. Cause to print a simple function index. This is done by assembling a list of function names, file names on which each function is defined, the line numbers where each function name occurs, and the text of each line. The list is then printed on the stan- dard output. No tags file is created or changed. Produce a page index on the standard output. This listing contains the function name, file name, and page number within that file (assuming 56-line pages to match pr(1)). Files whose name ends in or are assumed to be C source files and are searched for C routine and macro definitions. Others are first exam- ined to see if they contain any Pascal or FORTRAN routine definitions; if not, they are processed again looking for C definitions. Other options are: Use forward searching patterns (default). Use backward searching patterns Add the information from the files to the tags file. Unlike re-building the tags file from the original files, this can cause the same symbol to be entered twice in the tags file. This option should be used with caution and then only in very special circumstances. Create tags for typedefs. Suppress warning diagnostics. Update the specified files in tags; that is, all references to those files are deleted, and the new values are added to the file as in above. (Beware: this option is implemented in a way which is rather slow; it is usually faster to simply rebuild the tags file.) The tag is treated specially in C programs. The tag formed is created by adding to the beginning of name of the file, with any trailing removed, and leading pathname components also removed. This makes use of practical in directories with more than one program. EXTERNAL INFLUENCES
Environment Variables determines the order in which the output is sorted. determines the interpretation of the single- and/or multi-byte characters within comments and string literals. If or is not specified in the environment or is set to the empty string, the value of is used as a default for each unspecified or empty variable. If is not specified or is set to the empty string, a default of ``C'' (see lang(5)) is used instead of If any internationaliza- tion variable contains an invalid setting, behaves as if all internationalization variables are set to ``C''. See environ(5). International Code Set Support Single- and multi-byte character code sets are supported with the exception that multi-byte character file names are not supported. DIAGNOSTICS
An attempt to get additional heap space failed; the sort could not be performed. The tags file may be incorrect. A character was found unexpectedly in the first column. This can lead to incorrect entries in the tags file. The same name was detected twice in the same file. A tags entry was made only for the first name found. The same name was detected in two different files. A tags entry was made only for the first name found. EXAMPLES
Create a tags file named in the current directory for all C source files and all header files in the current directory: Once the tags file exists in the current directory, it can be used with commands that support tag files (such as (see vi(1)). Use the tags file with to edit a particular function located in one of the source files: While editing a C source file using use the tag command to edit function Use to find in file While using find in file (does not have to be the file currently being edited): WARNINGS
Recognition of and for FORTRAN and Pascal is done in a very simple way. No attempt is made to deal with block structure; if there are two Pascal procedures in different blocks with the same name, a warning message is generated. The method of deciding whether to look for C or Pascal and FORTRAN functions is an approximation, and can be fooled by unusual programs. does not know about and Pascal types. It relies on the input being well formed to detect typedefs. Use of shows only the last line of typedefs. is naive about tags files with several identical tags; it simply chooses the first entry its (non-linear) search finds with that tag. Such files can be created with either the or options or by editing a tags file. If more than one (function) definition appears on a single line, only the first definition is indexed. AUTHOR
was developed by the University of California, Berkeley. FILES
output tags file temporary file used by SEE ALSO
ex(1), vi(1). STANDARDS CONFORMANCE
ctags(1)
All times are GMT -4. The time now is 01:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy