ELinks 0.18.0
history.h File Reference
This graph shows which files directly or indirectly include this file:

Data Structures

struct  ses_history
 

Functions

void create_history (struct ses_history *history)
 
void destroy_history (struct ses_history *history)
 
void clean_unhistory (struct ses_history *history)
 
void add_to_history (struct ses_history *history, struct location *loc)
 
void del_from_history (struct ses_history *history, struct location *loc)
 
void go_history (struct session *ses, struct location *loc)
 Note that this function is dangerous, and its results are sort of unpredictable.
 
int go_history_by_n (struct session *ses, int n)
 Move back -n times if n is negative, forward n times if positive.
 
void go_back (struct session *ses)
 Go backward in the history.
 
void go_unback (struct session *ses)
 Go forward in the history.
 
void ses_history_move (struct session *ses)
 

Function Documentation

◆ add_to_history()

void add_to_history ( struct ses_history * history,
struct location * loc )
related

◆ clean_unhistory()

void clean_unhistory ( struct ses_history * history)
related

◆ create_history()

void create_history ( struct ses_history * history)
related

◆ del_from_history()

void del_from_history ( struct ses_history * history,
struct location * loc )
related

◆ destroy_history()

void destroy_history ( struct ses_history * history)
related

◆ go_back()

void go_back ( struct session * ses)

Go backward in the history.

See go_history() description regarding unpredictable effects on cur_loc() by this function.

◆ go_history()

void go_history ( struct session * ses,
struct location * loc )

Note that this function is dangerous, and its results are sort of unpredictable.

If the document is cached and is permitted to be fetched from the cache, the effect of this function is immediate and you end up with the new location being cur_loc(). BUT if the cache entry cannot be used, the effect is delayed to the next main loop iteration, as the TASK_HISTORY session task (ses_history_move()) is executed not now but in the bottom-half handler. So, you MUST NOT depend on cur_loc() having an arbitrary value after call to this function (or the regents go_(un)back(), of course).

◆ go_history_by_n()

int go_history_by_n ( struct session * ses,
int n )

Move back -n times if n is negative, forward n times if positive.

◆ go_unback()

void go_unback ( struct session * ses)

Go forward in the history.

See go_history() description regarding unpredictable effects on cur_loc() by this function.

◆ ses_history_move()

void ses_history_move ( struct session * ses)