> On Wed, 15 Aug 2012, Isaac wrote:
>
>
> It also seem reasonable to assume that if tic *really* fails, it will
> return an error (non-0)... I would be ok with removing these invalid
> 'after-checks'.
Note that it compiles it, but returns 127.
>> (Note: tic -s -v10 gives these errors:
>> ===
>> $ tic -s -v10 /usr/dt/config/dtterm.ti
>> "/usr/dt/config/dtterm.ti", line 1, terminal 'dtterm': Conflicting key
>> definitions (using the last) ... KEY_F(15) is the same as KEY_HELP
>> "/usr/dt/config/dtterm.ti", line 1, terminal 'dtterm':
>> exit_attribute_mode differs from sgr(0) exit_attribute_mode="\e[0m"
>>        sgr(0)="\e[0m\^O"
>> "/usr/dt/config/dtterm.ti", line 1, 'dtterm' tic: symbol lookup error:
>> tic: undefined symbol: _tracef
>> ===
>> and exits with $? = 127)
>>
>
> Hmm, my terminfo-foo skills are rusty, but I think the ^O in sgr0
> means to switch out of extended character mode, which I believe is
> desireable for sgr (Set Graphic Rendition)... Not sure why it thinks
> sgr0 and exit_attribute_mode must be thae same.  No idea what _tracef
> is, and I thought HELP was typically F1 on pc-style kb mappings.  Does
> tic exit with an error without the -s -v10 options?  Could it be that
These are purely for debugging:
-s     Summarize  the  compile  by  showing  the  directory  into which
entries are written, and the number of entries  which  are  compiled.

-vn  specifies that (verbose) output be written to standard error trace
information showing tic's progress.  The optional parameter n is a number 
from  1  to 10, inclusive, indicating the desired level of detail of
information.  If n is omitted, the default level  is  1. If  n  is 
specified  and  greater  than 1, the level of detail is increased.

> is why this check for /usr/share{,/lib}/terminfo/d/dtterm was added?
It looks like this is mostly for the sake of running chown bin:bin.



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel

Reply via email to