Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two-way history file handling #4

Open
GoogleCodeExporter opened this issue Apr 1, 2015 · 4 comments
Open

Two-way history file handling #4

GoogleCodeExporter opened this issue Apr 1, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

At the moment, system history is loaded once on program startup. The goal is 
to create a file monitor which will ensure program gets updated history list 
on every terminal command. Also whenever command is executed from program 
itself history file will be saved so terminal application could use it.

Original issue reported on code.google.com by MeanEYE.rcf on 29 May 2010 at 9:14

@GoogleCodeExporter
Copy link
Author

Original comment by MeanEYE.rcf on 19 Feb 2012 at 4:56

  • Added labels: Milestone-Release0.2
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Something like .bash_history or, I don't get it right.

Original comment by archenr...@gmail.com on 12 May 2013 at 10:11

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

At the moment if you start typing in the command entry in main window, 
Sunflower will poorly try to complete your command based on entries in your 
bash history. Two-way history handling refers to cases when you execute a 
command using Sunflower, from command entry or terminal window, that command 
will be applied to history file.

Original comment by MeanEYE.rcf on 12 May 2013 at 10:15

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Hm, I'll try to examine it and think :-))

Original comment by archenr...@gmail.com on 13 May 2013 at 7:54

  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant