![]() |
|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
![]() |
|
Thread Tools | Display Modes |
|
|||
![]()
ls program in bsd display all the contents in the current directory but some file are directories. I know with the option ls -F can differentiate between them. Then I come out the question, can i modify the ls program to display the directory in color and others remain the same just like Linux
![]() Last edited by bsdnewbie999; 5th May 2009 at 02:11 PM. Reason: should be program not command. |
|
|||
![]()
OpenBSD's ls(1) does not support colours, but if really require such a ridiculous feature.. someone has created a modified version, you can find it in the ports tree.
Here is shortcut: sysutils/colorls |
|
|||
![]() Quote:
|
|
|||
![]()
I beg to differer, that's what file(1) is for.. there is no point arguing though, this is just my personal opinion.
|
|
||||
![]() Quote:
should behave the same. ![]() |
|
||||
![]() Quote:
If anyone requires syntax highlighting to write code, they probably do not know how to write code in the first place. If anyone requires colour output to tell directories from files, they are probably a dipstick. Simple.
__________________
My Journal Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''. |
|
|||
![]() Quote:
Now the question: why is using syntax highlighting to be considered a bad habit? And what are the strategies to make do without? tks |
|
|||
![]()
You may be taking the comments made in this thread a bit too literally.
There is nothing inherently evil about color syntax highlighting, however if it becomes a crutch such that you have to have it available, then this may become a problem when you have to migrate to systems which don't have your specific customizations configured. I use color syntax highlighting on occasions for similar reasons: it can help bring to focus certain aspects of structure, but I can also live without it. Emacs colors differently (by default) than vim, so because I have spent a lot of time in Emacs lately, suddenly moving to vim initially seems odd. Most editors make the colors configurable, but I don't find the default choices so distasteful in these environments to do anything about it. Besides, on OpenBSD systems, I tend to use mg(1) which doesn't provide color syntax highlighting at all. Also, it's better because it is faster. ![]() I suspect the consternation you may be reading in this thread result from the fact Linux distributions tend to have the output of ls(1) color-coded. Personally, I find this distracting, but that is my opinion, & preference. If others find it helpful, fine. This debate can quickly decay into a religious war which doesn't possess significant value. Now if you start treading on my ANSI color-fied shell prompt, then those are fighting words. ![]() So it's a question of what has been your experience, & what your choices are based upon that experience. Nothing more. If you like color-syntax highlighting great. If you don't, that's fine too. It's merely a feature. |
![]() |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Delayed command? | wubrgamer | Other BSD and UNIX/UNIX-like | 9 | 22nd April 2009 03:15 AM |
read & modify files out side chroot jail | Dr_Death_UAE | FreeBSD Security | 5 | 6th November 2008 09:20 PM |
Modify host-level firewall rules (without getting locked out) | anomie | Guides | 13 | 16th June 2008 04:26 AM |
Which light Gui from modify images files? | aleunix | OpenBSD General | 7 | 15th June 2008 04:32 PM |
How to modify the boot loader? | Sunsawe | FreeBSD General | 5 | 29th May 2008 05:13 AM |