On 29 Dec 1999 03:30:41 +0200, Samy Merchi <[EMAIL PROTECTED]> wrote:

[...]

> No,  I  am  using  a fixed font setting, actually. See, the conversion
> *removes*  the  asterisk or underscore, and thereby there's the effect
> of  a  'delete'  key  being  pressed -- the rest of the line moves one
> space  to  the  left,  messing  up stuff like tables and other aligned
> stuff.  Also,  if  I'm for example using asterisks as separators, they
> just vanish and instead bolden up what comes after.

Yes, this is pretty standard behaviour for dealing with email styles.
I agree that it should be optional, and I'm sure such an option will
be added as time permits.

> Gah.  Update.  It  appears  that at least in the new message window it
> *doesn't* remove the asterisks, simply boldens the space between them.
> IIRC, though, that's not how it works in the message reader window, in
> which  it *strips* the asterisks after boldening up the space between.
> If  that  isn't the case, I must have a severe case of misremembering,
> and I apologize.

When writing emails, Textinput.mcc is used. When reading emails, an
internal class is used. Unfortunately the behaviour between these two
classes is not consistent, which is another issue that will be
addressed in future.

> I do think, though, that this feature should have at the very least an
> on/off  checkmark  somewhere  in  the  settings,  if not more detailed
> configuration  options.  (Such  as  for example assigning which symbol
> converts to which enhancement, in case one tends to use another symbol
> than an asterisk to indicate boldface.)

Although I agree with having an option to disable the parsing of
styles, it would not at all be a good idea to allow the user to select
which characters relate to which styles. Obviously these choices
wouldn't be transmitted with the email, so there would be no way for
the recipient to view such emails correctly.

[...]

> Oh,  incidentally,  I think it would also be a nice feature if the new
> message  window  updated  the  message  body  area  when you exited an
> external  editor.  As  it  is,  I tend to go to the external editor to
> write  messages,  then  quit and save the external editor, look at the
> message window and it still has the old version, so I, being paranoid,
> end up always hitting the external editor a second time and quitsaving
> right  away,  just  to  get  the  textfield to update. Would it be too
> tricky to find a way for the textfield to sense if the external editor
> makes changes to the file, and update the textfield accordingly?

I assume you're talking about the "New message" window. Textinput has
this behaviour already, check your Textinput MUI preferences if this
isn't working for you. Also, be sure that you're using the latest
version of Textinput.mcc.
-- 
(====> Jerome "King Guppy" Fisher/Omniscient International <====)
Email: mailto:[EMAIL PROTECTED]
IRC: KingGuppy on Oz.org and Arcnet.
ICQ: 12597354
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>

Reply via email to