On Wed, Dec 1, 2010 at 8:48 PM, [email protected] <[email protected]> wrote:
> On Wed, Dec 1, 2010 at 7:39 AM, Tony Balinski <[email protected]> wrote:
>>> It's the last file opened that receives focus, as you say. Is this right? I
>>> don't know. It doesn't bother me.
>
>> I am curious why the question has been raised. Any issue with current
> behavior?
>
> Often I open many files on the command line using wildcards.
> Seems to me that bringing focus on last opened files it is right behavior when
> opened using UI.
> Opening by command line parameters, should be the first opened file to have
> the focus.

Why would you think so? To me, the last should have the focus.

> Is there a trick to automate/force the focus on a particular tab?

Maybe put the file you want to have the focus last?

> Tony Balinski wrote:
>> A binary file becomes read-only if NEdit cannot handle the content properly.
>> If all byte values are used in a file NEdit won't be able to find a
> substitute
>> for the null (code-point 0) character, which it uses as a string end marker.
>> If it can't use another character (internally) instead, it will just allow
> you
>> to look at the content, but not to change it - completely read-only. That is
>> the case for executables, corefiles etc. (I actually find viewing corefiles
>> with NEdit can be useful.)
>
> understand.
> Sometimes I need to open RAW and partially decoded emails with Nedit.
> When these RAW files are encoded, do not use all byte values and Nedit can
> open them in write mode.
> When these files are partially decoded (for example an attached image or word
> processor file), Nedit do not let me to simply delete the binary part, and
> edit the body text part or simply re-save the text only part.
>
> Is there a simple method to force write mode to only delete binary part and
> resave?
>
> thank you in advance,
> Valerio
>
> --
> NEdit Develop mailing list - [email protected]
> http://www.nedit.org/mailman/listinfo/develop
>
-- 
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop

Reply via email to