Searching in UNIX files - hits all show up on line 1 (solved)

Searching in UNIX files - hits all show up on line 1 (solved)

2

    Apr 12, 2011#1

    Long time UltraEdit user, first time poster. I'm using UE Version 16.30.0.1009. I have configured UE to convert all UNIX file types to DOS, but to save in original format. The most important thing here is that I preserve the original format when saving. I work with both DOS and UNIX file types.

    The problem is when you perform a "Find in Files" on a native UNIX file type, all hits in the output window are shown being on line 1. Obviously, when you double click to go to the hit, it only takes you to line 1. Is there a solution to this?

    I've just noticed that it only happens when you select "Project Files" for the "Search In:" selection. "Files Listed" and "Open Files" works okay.

    Here's an example:

    ----------------------------------------
    Find 'uint8_t' in 'c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_buffer.c':
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_buffer.c(1): void var_buffer_add8 ( var_buffer_t *p_buf, uint8_t i_byte )
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_buffer.c(1): uint8_t var_buffer_get8 ( var_buffer_t *p_buf )
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_buffer.c(1): uint8_t i_byte;
    Found 'uint8_t' 3 time(s).
    ----------------------------------------
    Find 'uint8_t' in 'c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd.c':
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd.c(1): uint8_t *pRsp;
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd.c(1): uint8_t data;
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd.c(1): data = (uint8_t)dsid;
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd.c(1): pRsp = (uint8_t *)&rcv_buf[pos];
    Found 'uint8_t' 4 time(s).
    ----------------------------------------
    Find 'uint8_t' in 'c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c':
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): static uint8_t OBD_data_1byte[NUM_1_BYTE_DIDS];
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): static uint8_t OBD_data_2byte[NUM_2_BYTE_DIDS][2];
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): static uint8_t OBD_data_4byte[NUM_4_BYTE_DIDS][4];
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): static uint8_t OBD_data_8byte[NUM_8_BYTE_DIDS][8];
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): uint8_t did = 0;
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): memcpy( (uint8_t *)(&(param->info)),
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): (uint8_t *)(&(obd_data_db[did].info)),
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): memcpy( (uint8_t *)(&(param->data)),
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): (uint8_t *)(obd_data_db[did].data_ptr),
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): memcpy( (uint8_t *)(&(obd_data_db[did].info)),
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): (uint8_t *)(&(param->info)),
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): memcpy( (uint8_t *)(obd_data_db[did].data_ptr),
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): (uint8_t *)(&(param->data)),
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): int LS_OBD_Process_Data_Set_Packet( uint8_t *dataset )
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): uint8_t datalen = dataset[3];
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): uint8_t i = 4;
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): uint8_t j;
    c:\projects\svn\widget\Apps\DataService\trunk_stw\ds_obd_db.c(1): uint8_t did;
    Found 'uint8_t' 18 time(s).

    Thanks!

    Stacey

      Apr 14, 2011#2

      As it turns out, it was a configuration issue and Troy from UE got me straightened out. Part of his response follows:
      Troy wrote:Please go to Advanced -> Configuration -> File Handling -> DOS/Unix/Mac Handling and ensure that "Only recognize DOS terminated lines (CR/LF) as new lines for editing) is NOT selected.
      Thanks!

      Stacey