Implementation of history file.
-- Saves in cscope.hist in the current working directory.
-- Automatically loading when starting from the same file
-- check to see if the string is already in history -- not allowing duplicates.
Mikhail,
I generally like the patch, A few thoughts though:
1) How does this work in a multiuser environment? I.e. if one cscope database is shared among many people in a read-only fashion. It may not be a big deal, but the perror output on save is going to be disconcerting to users I think
2) Simmilarly, cscope allows you to specify the input database used when searching (the -f option), but the search history is shared among all databases. does that make sense?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1 -- the patch will not work properly with mutliusers. The history file name would have to include the user name or uid. The history name file could be given via command line too. BTW I am surprised that people would use this in a multiuser env. ;-) but what do I know.
If you give me a few hints on this -- I will be happy to modify the patch.
2 currently the 'cscope.hist' file is saved in the current working directory.
Mikhail,
I generally like the patch, A few thoughts though:
1) How does this work in a multiuser environment? I.e. if one cscope database is shared among many people in a read-only fashion. It may not be a big deal, but the perror output on save is going to be disconcerting to users I think
2) Simmilarly, cscope allows you to specify the input database used when searching (the -f option), but the search history is shared among all databases. does that make sense?
[patches:#85] input history file.
Status: open
Group:
Labels: history
Created: Thu Apr 17, 2014 12:00 AM UTC by mikhail nefedov
Last Updated: Thu Apr 17, 2014 12:00 AM UTC
Owner: nobody
Implementation of history file.
-- Saves in cscope.hist in the current working directory.
-- Automatically loading when starting from the same file
-- check to see if the string is already in history -- not allowing duplicates.
Mikhail,
I generally like the patch, A few thoughts though:
1) How does this work in a multiuser environment? I.e. if one cscope database is shared among many people in a read-only fashion. It may not be a big deal, but the perror output on save is going to be disconcerting to users I think
2) Simmilarly, cscope allows you to specify the input database used when searching (the -f option), but the search history is shared among all databases. does that make sense?
Neil, thank you for the reply
1 -- the patch will not work properly with mutliusers. The history file name would have to include the user name or uid. The history name file could be given via command line too. BTW I am surprised that people would use this in a multiuser env. ;-) but what do I know.
If you give me a few hints on this -- I will be happy to modify the patch.
2 currently the 'cscope.hist' file is saved in the current working directory.
On Monday, April 21, 2014 1:29:32 PM, Neil Horman nhorman@users.sf.net wrote:
Mikhail,
I generally like the patch, A few thoughts though:
1) How does this work in a multiuser environment? I.e. if one cscope database is shared among many people in a read-only fashion. It may not be a big deal, but the perror output on save is going to be disconcerting to users I think
2) Simmilarly, cscope allows you to specify the input database used when searching (the -f option), but the search history is shared among all databases. does that make sense?
[patches:#85] input history file.
Status: open
Group:
Labels: history
Created: Thu Apr 17, 2014 12:00 AM UTC by mikhail nefedov
Last Updated: Thu Apr 17, 2014 12:00 AM UTC
Owner: nobody
Implementation of history file.
-- Saves in cscope.hist in the current working directory.
-- Automatically loading when starting from the same file
-- check to see if the string is already in history -- not allowing duplicates.
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/cscope/patches/85/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Patches: #85
fscanf() fix.