06-03-2019
Also, the old man page repo was giving about 10 - 15+ percent errors because it was so large and difficult to manage.
Now, that I am moving the man page text and keys to the SQL DB and rewritten the search algorithms, the error rate has dropped to 0.5 percent to 1.5 percent.
That is a huge improvement in results.
Also, since I have completely changed the search algorithm, I have completely eliminated the need for HTTP redirects completely, which was a flaw in the algorithm I wrote a decade ago.
Seriously, it's a huge improvement and will get even better when I rewrite the repo landing pages for each OS and create a new custom search function / page.
This User Gave Thanks to Neo For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I tried looking for the answer online and came up with only a few semi-answers as to why file and directory names are case sensitive in Unix. Right off the bat, I'll say this doesn't bother me. But I run into tons of Windows and OpenVMS admins in my day job who go batty when they have to deal... (3 Replies)
Discussion started by: deckard
3 Replies
2. Solaris
is there any way to determine the last command entered on a unix machine???
Thanx (3 Replies)
Discussion started by: mm00123
3 Replies
3. SuSE
When we login to any remote connections in SuSE Linux, say for example, telnet , the following line is displayed "Last Login : Date and time is displayed"
I would like to disable this. In SuSE 9, I could find the solution .
Please suggest me a solution to disable the line displayed for SuSE... (3 Replies)
Discussion started by: Laksmi
3 Replies
4. Shell Programming and Scripting
Hi All,
My question is how can i stop my users on system from deleting their history.
How can i stop the users from running 'history -c'.
I have searched thoroughly on the forum but didn't find any satisfactory solution to the problem.
kindly help if you any suggestions
Thanx in... (3 Replies)
Discussion started by: xander
3 Replies
5. UNIX and Linux Applications
Hi everybody Im Megadrink!!!
This is my first thred.
Ive recently been introduced to Unix and i was interested in Unix's History. Can anyone give me a breif History On Unix. Just when it was invented/released. Maybe someother cool things about it.
Thx for the information in advance!! :D (2 Replies)
Discussion started by: Megadrink
2 Replies
6. Linux
Hi All,
Is there a way to check command executed by users in Linux for a specific date? I know we can use history, but it doesn't shows yesterday's executed commands.
rgds, (3 Replies)
Discussion started by: ronny_nch
3 Replies
7. UNIX for Dummies Questions & Answers
Hello All, Good Morning.
I am trying to erase history list in my linux box, but my below command is failing. What is the actual way to clear it?
> history clear
-bash: history: clear: numeric argument required
Also when I run my commands in my command prompt, my team lead can see my... (7 Replies)
Discussion started by: NARESH1302
7 Replies
8. Shell Programming and Scripting
commands to view the history file in unix.
I am not sure whether it is bash_history.sh (1 Reply)
Discussion started by: ramkumar15
1 Replies
9. What is on Your Mind?
I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX.
The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
10. UNIX for Advanced & Expert Users
hello all
i have application which according to AWS monitoring is reaching to high spikes of IO at random time .
and causing the server to crash and restart .
my question is how can i find out what cause the spike and if i can't with the native linux tools
what free open source minimon... (6 Replies)
Discussion started by: umen
6 Replies
LEARN ABOUT MOJAVE
tklib_history
history(n) Provides a history for Entry widgets history(n)
__________________________________________________________________________________________________________________________________________________
NAME
history - Provides a history for Entry widgets
SYNOPSIS
package require Tcl 8.4
package require Tk 8.4
package require history ?0.1?
::history::init pathName ?length?
::history::remove pathName
::history::add pathName text
::history::get pathName
::history::clear pathName
::history::configure pathName option ?value?
bell
_________________________________________________________________
DESCRIPTION
This package provides a convenient history mechanism for Entry widgets. The history may be accessed with the up and down arrow keys.
::history::init pathName ?length?
Arranges to remember the history of the named Entry widget. An optional length determines the number of history entries to keep.
This may be changed later with ::history::configure. History entries must be added with the ::history::add command before they can
be seen.
::history::remove pathName
Forgets all history entries for the Entry pathName and removes the history bindings.
::history::add pathName text
This command is used to add history entries to an Entry that has previously had ::history::init called on it. This command should be
called from your Entry handler with the contents of the entry (or whatever you wish to add to the history).
::history::get pathName
This command returns a list containing the history entries for the Entry pathName
::history::clear pathName
This command clears the history list for the named Entry.
::history::configure pathName option ?value?
This command queries or sets configuration options. Currently the options recognized are length and alert. Setting the length deter-
mines the number of history entries to keep for the named Entry. Alert specifies the command to run when the user reaches the end of
the history, it defaults to
bell
entry .e
bind .e <Return> [list ProcessEntry %W]
::history::init .e
pack .e
proc ProcessEntry {w} {
set text [$w get]
if {$text == ""} { return }
::history::add $w $text
puts $text
$w delete 0 end
}
KEYWORDS
entry, history
history 0.1 history(n)