Sponsored Content
Full Discussion: print only comments
Top Forums Shell Programming and Scripting print only comments Post 302429175 by pseudocoder on Sunday 13th of June 2010 10:10:41 AM
Old 06-13-2010
Yeah, because I (apart from the Perl script) only helped you to solve this problem:
# but I want to check if file is .java or .c++ not a simple file (-f), I don't know how to do it..

The part with awk and regex (the hardest part IMHO) is still open.
This User Gave Thanks to pseudocoder For This Post:
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Remove comments...

It may be a no-brainer, but the answer is escaping me right now: I'm trying to write a little script to remove all comments from .c source... I was thinking sed, but I'm not a very strong regexp user (e.g. I suck with sed). I tried dumping the file into: sed -e 's/\/\* * \*\///g' and several... (1 Reply)
Discussion started by: LivinFree
1 Replies

2. UNIX for Dummies Questions & Answers

Print comments in FTP

Dear Unix Gurus, Not sure if this is possible/workable but I'm trying add a comment line before each operation such as the following: ftp -n <mail server> ${log_dir}/test_put.log << END user <user_id> <password> verbose bin # List Files Before putting Data echo File Check Before FTP >>... (7 Replies)
Discussion started by: lweegp
7 Replies

3. Shell Programming and Scripting

Comments unexpectedly print

Hi All, I am working on a sh script. Half way through the script, my comments start to print to screen as if I used echo. Obviously any comments are preceded with a #. And I have not used set -x or anything similar. Can anyone free me of this simple but annoying problem? Thanks John (5 Replies)
Discussion started by: John H
5 Replies

4. Programming

lint comments

Hi can anyone help me regarding the meaning of the following lint messages. what is the use of having such lint comments in the c program. /*lint -esym(534,cputs,fgets,cprintf) */ /*lint -efile(766,pragmas.h) */ Thanks a lot in advance. (5 Replies)
Discussion started by: axes
5 Replies

5. Shell Programming and Scripting

Scripting comments

Anyone have a good link for documentation conventions for scripts? (4 Replies)
Discussion started by: gliesian
4 Replies

6. Shell Programming and Scripting

delete comments

Delete everything comes in between /* & */. Current File: ==================== create or replace procedure test421 is begin /* ---sasasas/*dsdsds */ dbms_output.put_line('SAURABH'); END; To be File: =================== create or replace procedure test421 is begin... (10 Replies)
Discussion started by: susau_79
10 Replies

7. Shell Programming and Scripting

Sed script, changing all C-comments to C++-comments

I must write a script to change all C++ like comments: // this is a comment to this one /* this is a comment */ How to do it by sed? With file: #include <cstdio> using namespace std; //one // two int main() { printf("Example"); // three }//four the result should be: (2 Replies)
Discussion started by: black_hawk
2 Replies

8. UNIX for Dummies Questions & Answers

Delete Comments

Hello i am back :D, i have a prolem. I want to Delete the IPs which are in Comments. Input 192.168.0.1 192.168.0.2 #192.168.0.3 #192.168.0.4 - when TAB or Space, delete too. /*192.168.0.5 192.168.0.6 192.168.0.7*\ Output 192.168.0.1 192.168.0.2 My solution is sed -e... (7 Replies)
Discussion started by: eightball
7 Replies
GIT-CHECK-ATTR(1)						    Git Manual							 GIT-CHECK-ATTR(1)

NAME
git-check-attr - Display gitattributes information SYNOPSIS
git check-attr [-a | --all | attr...] [--] pathname... git check-attr --stdin [-z] [-a | --all | attr...] < <list-of-paths> DESCRIPTION
For every pathname, this command will list if each attribute is unspecified, set, or unset as a gitattribute on that pathname. OPTIONS
-a, --all List all attributes that are associated with the specified paths. If this option is used, then unspecified attributes will not be included in the output. --cached Consider .gitattributes in the index only, ignoring the working tree. --stdin Read file names from stdin instead of from the command-line. -z Only meaningful with --stdin; paths are separated with a NUL character instead of a linefeed character. -- Interpret all preceding arguments as attributes and all following arguments as path names. If none of --stdin, --all, or -- is used, the first argument will be treated as an attribute and the rest of the arguments as pathnames. OUTPUT
The output is of the form: <path> COLON SP <attribute> COLON SP <info> LF <path> is the path of a file being queried, <attribute> is an attribute being queried and <info> can be either: unspecified when the attribute is not defined for the path. unset when the attribute is defined as false. set when the attribute is defined as true. <value> when a value has been assigned to the attribute. EXAMPLES
In the examples, the following .gitattributes file is used: *.java diff=java -crlf myAttr NoMyAttr.java !myAttr README caveat=unspecified o Listing a single attribute: $ git check-attr diff org/example/MyClass.java org/example/MyClass.java: diff: java o Listing multiple attributes for a file: $ git check-attr crlf diff myAttr -- org/example/MyClass.java org/example/MyClass.java: crlf: unset org/example/MyClass.java: diff: java org/example/MyClass.java: myAttr: set o Listing all attributes for a file: $ git check-attr --all -- org/example/MyClass.java org/example/MyClass.java: diff: java org/example/MyClass.java: myAttr: set o Listing an attribute for multiple files: $ git check-attr myAttr -- org/example/MyClass.java org/example/NoMyAttr.java org/example/MyClass.java: myAttr: set org/example/NoMyAttr.java: myAttr: unspecified o Not all values are equally unambiguous: $ git check-attr caveat README README: caveat: unspecified SEE ALSO
gitattributes(5). GIT
Part of the git(1) suite Git 1.8.3.1 06/10/2014 GIT-CHECK-ATTR(1)
All times are GMT -4. The time now is 11:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy