Yeah, this is how mine looked too, when I turned it on.  That's why I
said I thought the $scroll variables had to be messed with.

-Tom Hundt


Christof Boeckler wrote:
> Thanks!
>
> *Now* everything works, but until I changed the settings in setup (from
> narrow, no splitter to something else and back) my scrollbar looked like
> this:
>
> http://jamesie.de/tmp/useless.png
>
> i.e. rather useless, although I had over 70 lines. At first I thought it
> was because of my new bigger screen (1600x1200 res.). But now it works fine.
> The screenshot above looks like a little bug to me.
>
> Christof
>
> Jon Green schrieb:
>>
>> Christof Boeckler wrote:
>>  > Hi!
>>  > Long time - no mail :-)
>>  >
>>  > I don't remember the time when I first noticed this, but at the
>> moment my
>>  > ME lacks a vertical scroll bar. Is this a configurable feature or more
>>  > some king of buggy behaviour?
>>  > If configurable, how can I reenable it?
>>  >
>>
>> M-x user-setup
>> Platform->Scroll Bars
>>
>> Jon.
>>
>>
>
>
> Gruß
>         Christof Böckler
>
--
Thomas Hundt <tom@...> +1-415-867-6698

On Tue 10/03/09  4:48 PM , "Christof Boeckler" microemacs@... sent:
> Thanks!
>
> *Now* everything works, but until I changed the settings in setup (from
> narrow, no splitter to something else and back) my scrollbar looked like
> this:
>
> http://jamesie.de/tmp/useless.png
> i.e. rather useless, although I had over 70 lines. At first I thought it
> was because of my new bigger screen (1600x1200 res.). But now it works
> fine.The screenshot above looks like a little bug to me.
>
> Christof

Ah OK. Agreed that is not very clever.

Does not do that in my version here but then again it has been patched on
numerous occasions and so has likely been fixed.

We really need to splash another release.

Jon.




>
> Jon Green schrieb:
> >
> >
> > Christof Boeckler wrote:
> >  > Hi!
> >  > Long time - no mail :-)
> >  >
> >  > I don't remember the time when I first
> noticed this, but at the > moment my
> >  > ME lacks a vertical scroll bar. Is this a
> configurable feature or more>  > some king of buggy behaviour?
> >  > If configurable, how can I reenable
> it?>  >
> >
> > M-x user-setup
> > Platform->Scroll Bars
> >
> > Jon.
> >
> >
>
>
> Gruß
> Christof Böckler
>
>
> Gruß
> Christof Böckler
>
> --
> What is money? http://moneyasdebt.net/
>
> ------------------------------------
>
> __________________________________________________________________________
> This is an unmoderated list, but new members are moderated to ensure that
> there are no spam users. JASSPA is not responsible for the content of any
material posted to this list.
>
> To un-subscribe, send a mail message to
>
> jasspa-unsubscribe@yahoogroups.com
> or visit http://groups.yahoo.com/group/jasspa andmodify your account settings
manually.
>
>
> Yahoo! Groups Links
>
> Individual Email | Traditional
>
> jasspa-unsubscribe@yahoogroups.com
>
>
---- Message sent via KC WebMail - http://webmail.mistral.net/

Jon Green wrote:
>
>
>  On Tue 10/03/09  4:48 PM , "Christof Boeckler" microemacs@... sent:
>> Thanks!
>>
>> *Now* everything works, but until I changed the settings in setup (from
>> narrow, no splitter to something else and back) my scrollbar looked like
>> this:
>>
>> http://jamesie.de/tmp/useless.png
>> i.e. rather useless, although I had over 70 lines. At first I thought it
>> was because of my new bigger screen (1600x1200 res.). But now it works
>> fine.The screenshot above looks like a little bug to me.
>>
>> Christof
>
> Ah OK. Agreed that is not very clever.
>
> Does not do that in my version here but then again it has been patched on
numerous occasions and so has likely been fixed.
>
> We really need to splash another release.

I've posted a development snapshot on the site.

http://www.jasspa.com/development/me20090310_dev_snapshot/

There is also a pre-built Windows binary. If you have a Windows install
from InstallShield the simple way to update is to over-write the
me32.exe and macro files in c:/Program Files/Jasspa/MicroEmacs with the new.

Jon.

Hey has anyone done anything along the lines of making a native Mac
version?  By native I mean not X11, which works great, but using their
real window manager, Carbon or whatever they call it.  There's a bit of
extra functionality that could be gained by this: being able to drag and
drop onto a running window, better clipboard functionality, etc.


Jon Green wrote:
>
>
>  On Tue 10/03/09  4:48 PM , "Christof Boeckler" microemacs@... sent:
>> Thanks!
>>
>> *Now* everything works, but until I changed the settings in setup (from
>> narrow, no splitter to something else and back) my scrollbar looked like
>> this:
>>
>> http://jamesie.de/tmp/useless.png
>> i.e. rather useless, although I had over 70 lines. At first I thought it
>> was because of my new bigger screen (1600x1200 res.). But now it works
>> fine.The screenshot above looks like a little bug to me.
>>
>> Christof
>
> Ah OK. Agreed that is not very clever.
>
> Does not do that in my version here but then again it has been patched on
numerous occasions and so has likely been fixed.
>
> We really need to splash another release.
>
> Jon.
>
>
>
>
>> Jon Green schrieb:
>>>
>>> Christof Boeckler wrote:
>>>  > Hi!
>>>  > Long time - no mail :-)
>>>  >
>>>  > I don't remember the time when I first
>> noticed this, but at the > moment my
>>>  > ME lacks a vertical scroll bar. Is this a
>> configurable feature or more>  > some king of buggy behaviour?
>>>  > If configurable, how can I reenable
>> it?>  >
>>> M-x user-setup
>>> Platform->Scroll Bars
>>>
>>> Jon.
>>>
>>>
>>
>> Gruß
>> Christof Böckler
>>
>>
>> Gruß
>> Christof Böckler
>>
>> --
>> What is money? http://moneyasdebt.net/
>>
>> ------------------------------------
>>
>> __________________________________________________________________________
>> This is an unmoderated list, but new members are moderated to ensure that
>> there are no spam users. JASSPA is not responsible for the content of any
material posted to this list.
>>
>> To un-subscribe, send a mail message to
>>
>> jasspa-unsubscribe@yahoogroups.com
>> or visit http://groups.yahoo.com/group/jasspa andmodify your account settings
manually.
>>
>>
>> Yahoo! Groups Links
>>
>> Individual Email | Traditional
>>
>> jasspa-unsubscribe@yahoogroups.com
>>
>>
> ---- Message sent via KC WebMail - http://webmail.mistral.net/
>
>
> ------------------------------------
>
> __________________________________________________________________________
>
> This is an unmoderated list, but new members are moderated to ensure that
there are no spam users. JASSPA is not responsible for the content of
> any material posted to this list.
>
> To un-subscribe, send a mail message to
>
>     mailto:jasspa-unsubscribe@yahoogroups.com
>
> or visit http://groups.yahoo.com/group/jasspa and
> modify your account settings manually.
>
>
> Yahoo! Groups Links
>
>
>
--
Thomas Hundt <tom@...> +1-415-867-6698

Thomas Hundt wrote:
> Hey has anyone done anything along the lines of making a native Mac
> version?  By native I mean not X11, which works great, but using their
> real window manager, Carbon or whatever they call it.  There's a bit of
> extra functionality that could be gained by this: being able to drag and
> drop onto a running window, better clipboard functionality, etc.
>

Hi Thomas,

I'm afraid not. We have been so busy we have not made any releases of
just the base stuff so Mac seems a long way away.

Jon.

Hi list,

I have a serious problem with ME window sizing behaviour. I can't
remember exactly when it emerged, but I am quite sure that it is related
to my recently growing screen resolutions. I went from 1024x768 to
1280x1024 an the problems began if I remember correctly. Lately I even
switched to 1600x1200 and here's the mess:

When I start me it seems impossible to tell it wich screen size it shoult
have not to speakof the position.
First I tried the generic X option -geometry but me doesn't support this
option.
Then I tried to store the frame size from inside me. At the next start
every size and position is possible, from tiny to ridiculusly huge windows.
My last resort was to set the X properties of me with no effect. (I use
IceWM on Linux and it has the ability to specify per window sizing
options in the -geometry option style.)

If I maximise me I get the following variable values:
     $frame-depth .................. "57"
     $frame-width .................. "159"
     $window-depth ................. "26"
     $window-width ................. "158"

I am definitely annoyed by resizing me everytime I start it. Is this
expected behaviour or simply a bug? Is there hope or help?

Christof

I need to correct myself:

After having stored the frame size (from within the modeline) the window
size is reliably the same. But still the position of the newly created
window can't be controlled in advance. Once it's top left, next time
hanging out of the lower right corner or vice versa.
Implementing the -geometry option would solve this issue I guess.
Any ideas?

Christof

Christof Boeckler schrieb:
> Hi list,
>
> I have a serious problem with ME window sizing behaviour. I can't
> remember exactly when it emerged, but I am quite sure that it is related
> to my recently growing screen resolutions. I went from 1024x768 to
> 1280x1024 an the problems began if I remember correctly. Lately I even
> switched to 1600x1200 and here's the mess:
>
> When I start me it seems impossible to tell it wich screen size it shoult
> have not to speakof the position.
> First I tried the generic X option -geometry but me doesn't support this
> option.
> Then I tried to store the frame size from inside me. At the next start
> every size and position is possible, from tiny to ridiculusly huge windows.
> My last resort was to set the X properties of me with no effect. (I use
> IceWM on Linux and it has the ability to specify per window sizing
> options in the -geometry option style.)
>
> If I maximise me I get the following variable values:
> $frame-depth ............ ...... "57"
> $frame-width ............ ...... "159"
> $window-depth ............ ..... "26"
> $window-width ............ ..... "158"
>
> I am definitely annoyed by resizing me everytime I start it. Is this
> expected behaviour or simply a bug? Is there hope or help?
>
> Christof

Christof Boeckler wrote:
> Hi list,
>
> I have a serious problem with ME window sizing behaviour. I can't
> remember exactly when it emerged, but I am quite sure that it is related
> to my recently growing screen resolutions. I went from 1024x768 to
> 1280x1024 an the problems began if I remember correctly. Lately I even
> switched to 1600x1200 and here's the mess:
>
> When I start me it seems impossible to tell it wich screen size it shoult
> have not to speakof the position.
> First I tried the generic X option -geometry but me doesn't support this
> option.
> Then I tried to store the frame size from inside me. At the next start
> every size and position is possible, from tiny to ridiculusly huge windows.
> My last resort was to set the X properties of me with no effect. (I use
> IceWM on Linux and it has the ability to specify per window sizing
> options in the -geometry option style.)
>
> If I maximise me I get the following variable values:
>     $frame-depth .................. "57"
>     $frame-width .................. "159"
>     $window-depth ................. "26"
>     $window-width ................. "158"
>
> I am definitely annoyed by resizing me everytime I start it. Is this
> expected behaviour or simply a bug? Is there hope or help?
>
> Christof
>

I use a .Xdefaults file when running on Sun Solaris as follows and have
no problems as below.

Jon.

Dtwm*VCLSalFrame*secondariesOnTop: True
!######################################################################
!#                                                                    #
!# Defaults for MicroEmacs startup                                    #
!#                                                                    #
!######################################################################
!# MicroEmacs.font: <fontname>
!# Set the default font.
!# MicroEmacs.font: -*-lucidatypewriter-medium-r-*-*-*-120-*-*-m-*-*-*
MicroEmacs.font: -*-clean-medium-r-*-*-*-130-*-*-*-*-*-*

!# MicroEmacs.geometry: <char-width>x<char-height> {+/-}<xoffset>
{+-}<yoffset>
!# Set up the default screen size and position.
!# 102x65 characters please, 30 pixels from top left
MicroEmacs.geometry: 102x65 30 30

!# MicroEmacs.name: <name>
!# The name displayed in the title bar format is <name>: <file>
MicroEmacs.name: JASSPAs MicroEmacs

!# MicroEmacs: <icon-name>
!# The name displayed when MicroEmacs is iconized
MicroEmacs.iconname: JASSPAs MicroEmacs

Jon,

thanks for your reply!
I tried your settings but they did not solve my problem although it has
some effect.
The problem seems to be at a different level because the settings in
.Xdefaults only have an effect if I start ME from a terminal. If I start
it through a keyboard shortcut it looks different (size, position).
I need to explore this further ...

Christof

Jon Green schrieb:
> I use a .Xdefaults file when running on Sun Solaris as follows and have
> no problems as below.
>
> Jon.
>
> Dtwm*VCLSalFrame* secondariesOnTop : True
> !########### ######### ######### ######### ######### ######### #########
> #####
> !# #
> !# Defaults for MicroEmacs startup #
> !# #
> !########### ######### ######### ######### ######### ######### #########
> #####
> !# MicroEmacs.font: <fontname>
> !# Set the default font.
> !# MicroEmacs.font: -*-lucidatypewriter -medium-r- *-*-*-120- *-*-m-*-* -*
> MicroEmacs.font: -*-clean-medium- r-*-*-*-130- *-*-*-*-* -*
>
> !# MicroEmacs.geometry : <char-width> x<char-height> {+/-}<xoffset>
> {+-}<yoffset>
> !# Set up the default screen size and position.
> !# 102x65 characters please, 30 pixels from top left
> MicroEmacs.geometry : 102x65 30 30
>
> !# MicroEmacs.name: <name>
> !# The name displayed in the title bar format is <name>: <file>
> MicroEmacs.name: JASSPAs MicroEmacs
>
> !# MicroEmacs: <icon-name>
> !# The name displayed when MicroEmacs is iconized
> MicroEmacs.iconname : JASSPAs MicroEmacs

Christof Boeckler wrote:
> Jon,
>
> thanks for your reply!
> I tried your settings but they did not solve my problem although it has
> some effect.
> The problem seems to be at a different level because the settings in
> .Xdefaults only have an effect if I start ME from a terminal. If I start
> it through a keyboard shortcut it looks different (size, position).
> I need to explore this further ...
>
> Christof

Hi Christof,

OK edit the *.erf and delete the lines

   "frame-depth" = "86"
   "frame-width" = "168"

I think these are set when you right click on the toolbar line and there
is an option called "Store Frame Size". I never use this so my values
are not set in my .erf.

Best to shut down all instances of "me" and then use gedit, ne or
something to hack the .erf file to delete the lines. Then when you run
up again the .Xdefaults will have priority.

Hope that helps
Jon.


>
> Jon Green schrieb:
>> I use a .Xdefaults file when running on Sun Solaris as follows and have
>> no problems as below.
>>
>> Jon.
>>
>> Dtwm*VCLSalFrame* secondariesOnTop : True
>> !########### ######### ######### ######### ######### ######### #########
>> #####
>> !# #
>> !# Defaults for MicroEmacs startup #
>> !# #
>> !########### ######### ######### ######### ######### ######### #########
>> #####
>> !# MicroEmacs.font: <fontname>
>> !# Set the default font.
>> !# MicroEmacs.font: -*-lucidatypewriter -medium-r- *-*-*-120- *-*-m-*-* -*
>> MicroEmacs.font: -*-clean-medium- r-*-*-*-130- *-*-*-*-* -*
>>
>> !# MicroEmacs.geometry : <char-width> x<char-height> {+/-}<xoffset>
>> {+-}<yoffset>
>> !# Set up the default screen size and position.
>> !# 102x65 characters please, 30 pixels from top left
>> MicroEmacs.geometry : 102x65 30 30
>>
>> !# MicroEmacs.name: <name>
>> !# The name displayed in the title bar format is <name>: <file>
>> MicroEmacs.name: JASSPAs MicroEmacs
>>
>> !# MicroEmacs: <icon-name>
>> !# The name displayed when MicroEmacs is iconized
>> MicroEmacs.iconname : JASSPAs MicroEmacs
>
>
> ------------------------------------
>
> __________________________________________________________________________
>
> This is an unmoderated list, but new members are moderated to ensure that
there are no spam users. JASSPA is not responsible for the content of
> any material posted to this list.
>
> To un-subscribe, send a mail message to
>
>     mailto:jasspa-unsubscribe@yahoogroups.com
>
> or visit http://groups.yahoo.com/group/jasspa and
> modify your account settings manually.
>
>
> Yahoo! Groups Links
>
>
>
>

Jon Green schrieb:
> Christof Boeckler wrote:
>> Jon,
>>
>> thanks for your reply!
>> I tried your settings but they did not solve my problem although it has
>> some effect.
>> The problem seems to be at a different level because the settings in
>> .Xdefaults only have an effect if I start ME from a terminal. If I start
>> it through a keyboard shortcut it looks different (size, position).
>> I need to explore this further ...
>>
>> Christof
>
> Hi Christof,

Hi Jon,

> OK edit the *.erf and delete the lines
>
> "frame-depth" = "86"
> "frame-width" = "168"

I deleted those now.

> Best to shut down all instances of "me" and then use gedit, ne or
> something to hack the .erf file to delete the lines. Then when you run
> up again the .Xdefaults will have priority.

I tried to narrow down the cause of my problems systematically and found
out that settings in .Xdefaults have no effect.
Actually on my system the file .Xdefaults isn't even touched by ME (as
strace tells me), only a file .Xdefaults-thinkpad (thinkpad is my
hostname) is tried to be read (in accordance with X(7)). Setting up a
symlink .Xdefaults-thinkpad -> .Xdefaults doesn't change the behaviour,
although the file is read. (Your settings give me a 73x14+287+210 window.)

I wonder what the interface for setting windows sizes is (in regard to
the X server and/or window manager). With other applications (e.g.
Mozilla Thunderbird) I can perfectly set up geometry properties through
my window manager's configuration (similar to .Xdefaults). With ME it
does not work.

Is ME making any attempts to set its "window size" or is this totally up
to the window manager? Who is responsible for placing and sizing the ME
window? I really want this to be fixed.

>
> Hope that helps
> Jon.

Sorry, not yet.

Christof

Christof Boeckler wrote:
> Jon Green schrieb:
>> Christof Boeckler wrote:
>>> Jon,
>>>
>>> thanks for your reply!
>>> I tried your settings but they did not solve my problem although it has
>>> some effect.
>>> The problem seems to be at a different level because the settings in
>>> .Xdefaults only have an effect if I start ME from a terminal. If I start
>>> it through a keyboard shortcut it looks different (size, position).
>>> I need to explore this further ...
>>>
>>> Christof
>> Hi Christof,
>
> Hi Jon,
>
>> OK edit the *.erf and delete the lines
>>
>> "frame-depth" = "86"
>> "frame-width" = "168"
>
> I deleted those now.
>
>> Best to shut down all instances of "me" and then use gedit, ne or
>> something to hack the .erf file to delete the lines. Then when you run
>> up again the .Xdefaults will have priority.
>
> I tried to narrow down the cause of my problems systematically and found
> out that settings in .Xdefaults have no effect.
> Actually on my system the file .Xdefaults isn't even touched by ME (as
> strace tells me), only a file .Xdefaults-thinkpad (thinkpad is my
> hostname) is tried to be read (in accordance with X(7)). Setting up a
> symlink .Xdefaults-thinkpad -> .Xdefaults doesn't change the behaviour,
> although the file is read. (Your settings give me a 73x14+287+210 window.)
>
> I wonder what the interface for setting windows sizes is (in regard to
> the X server and/or window manager). With other applications (e.g.
> Mozilla Thunderbird) I can perfectly set up geometry properties through
> my window manager's configuration (similar to .Xdefaults). With ME it
> does not work.
>
> Is ME making any attempts to set its "window size" or is this totally up
> to the window manager? Who is responsible for placing and sizing the ME
> window? I really want this to be fixed.

The size is controlled by X-Windows via the X-Window resource management
and the size hints. My guess is that the likes of Thunderbird etc. are
controlled through some Gtk configuration rather than X-Windows.

The code that does this is in unixterm.c in function XTERMstart(). me
does not read the file directly, it is up to the window manager to
retrieve this information and then return it.

I cannot say that I have ever had a problem with this it has always
worked for me on Solaris, HP-UX and SGI. Cannot recall for Linux because
I do not use Linux much as a general working environment (I assume you
are on Linux) but cannot recall a problem.

For you to be using .Xdefaults-thinkpad then you must be running a
remote desktop.

I think you are going to have to trace this through, build a debug image
and then break from XTERMstart tracing it through to see what X returns
and how it is set up. Or use a few well chosen printf's temporarily to
see what is going on.

Regards
Jon.

>
>> Hope that helps
>> Jon.
>
> Sorry, not yet.
>
> Christof
>
>
> ------------------------------------
>
> __________________________________________________________________________
>
> This is an unmoderated list, but new members are moderated to ensure that
there are no spam users. JASSPA is not responsible for the content of
> any material posted to this list.
>
> To un-subscribe, send a mail message to
>
>     mailto:jasspa-unsubscribe@yahoogroups.com
>
> or visit http://groups.yahoo.com/group/jasspa and
> modify your account settings manually.
>
>
> Yahoo! Groups Links
>
>
>
>

Christof Boeckler wrote:
> Jon Green schrieb:
>> Christof Boeckler wrote:
>>> Jon,
>>>
>>> thanks for your reply!
>>> I tried your settings but they did not solve my problem although it has
>>> some effect.
>>> The problem seems to be at a different level because the settings in
>>> .Xdefaults only have an effect if I start ME from a terminal. If I start
>>> it through a keyboard shortcut it looks different (size, position).
>>> I need to explore this further ...
>>>
>>> Christof
>> Hi Christof,
>
> Hi Jon,
>
>> OK edit the *.erf and delete the lines
>>
>> "frame-depth" = "86"
>> "frame-width" = "168"
>
> I deleted those now.
>
>> Best to shut down all instances of "me" and then use gedit, ne or
>> something to hack the .erf file to delete the lines. Then when you run
>> up again the .Xdefaults will have priority.
>
> I tried to narrow down the cause of my problems systematically and found
> out that settings in .Xdefaults have no effect.
> Actually on my system the file .Xdefaults isn't even touched by ME (as
> strace tells me), only a file .Xdefaults-thinkpad (thinkpad is my
> hostname) is tried to be read (in accordance with X(7)). Setting up a
> symlink .Xdefaults-thinkpad -> .Xdefaults doesn't change the behaviour,
> although the file is read. (Your settings give me a 73x14+287+210 window.)
>
> I wonder what the interface for setting windows sizes is (in regard to
> the X server and/or window manager). With other applications (e.g.
> Mozilla Thunderbird) I can perfectly set up geometry properties through
> my window manager's configuration (similar to .Xdefaults). With ME it
> does not work.
>
> Is ME making any attempts to set its "window size" or is this totally up
> to the window manager? Who is responsible for placing and sizing the ME
> window? I really want this to be fixed.

The size is controlled by X-Windows via the X-Window resource management
and the size hints. My guess is that the likes of Thunderbird etc. are
controlled through some Gtk configuration rather than X-Windows.

The code that does this is in unixterm.c in function XTERMstart(). me
does not read the file directly, it is up to the window manager to
retrieve this information and then return it.

I cannot say that I have ever had a problem with this it has always
worked for me on Solaris, HP-UX and SGI. Cannot recall for Linux because
I do not use Linux much as a general working environment (I assume you
are on Linux) but cannot recall a problem.

For you to be using .Xdefaults-thinkpad then you must be running a
remote desktop.

I think you are going to have to trace this through, build a debug image
and then break from XTERMstart tracing it through to see what X returns
and how it is set up. Or use a few well chosen printf's temporarily to
see what is going on.

Regards
Jon.

>
>> Hope that helps
>> Jon.
>
> Sorry, not yet.
>
> Christof
>
>
> ------------------------------------
>
> __________________________________________________________
>
> This is an unmoderated list, but new members are moderated to ensure that there are no spam users. JASSPA is not responsible for the content of
> any material posted to this list.
>
> To un-subscribe, send a mail message to
>
> mailto:jasspa-unsubscribe@yahoogroups.com
>
> or visit http://groups.yahoo.com/group/jasspa and
> modify your account settings manually.
>
>
> Yahoo! Groups Links
>
>
>
>

Steven Phillips schrieb:
> The X function call used to get the start-up geometry info is:
>
>     XrmGetResource( rdb,"MicroEmacs. geometry" ,"MicroEmacs. Geometry"
> ,&retType,&retVal)

This function call returns 0. This means the requested resource was not
found, although I put exactly Jon's resource line in my .Xdefaults file (
and that was read through the symlink I created earlier today).

> As Jon says, the most likely cause is that Gtk is not honouring this
> original way of configuring X applications, have things moved on in the
> Linux world? So another possible way of resolving this is to find out
> what config files your Window manager does read and put a suitable
> configuration in one of those...

I tried to put the setting in such a file but no effect. In fact I
started doing this and stumbled upon this problem.

I will now try to find out, why IceWM is not honouring my settings.

> Steve

Thank you both for your help!

Christof

Hi,

In tcl the right keyword for an ''if' after an 'else' is
'elseif', so in tcl.eaf the line:

elif "elsif {\p} {\r\r}\P"  "  elif"
should be:
elif "elseif {\p} {\r\r}\P"  "  elif"

and my questions:

I'm using the 20090310 snapshot without any problem.
Is there any plan to release a newer snapshot to test, or
even a new release?

Is there anybody who is working on subversion support
macros? (similar to cvs.emf)


Thanks for your good work,
Ferenc Deak

Deak, Ferenc wrote:
> Hi,
>
> In tcl the right keyword for an ''if' after an 'else' is
> 'elseif', so in tcl.eaf the line:
>
> elif "elsif {\p} {\r\r}\P"  "  elif"
> should be:
> elif "elseif {\p} {\r\r}\P"  "  elif"
>
> and my questions:

Thanks for the update.

>
> I'm using the 20090310 snapshot without any problem.
> Is there any plan to release a newer snapshot to test, or
> even a new release?
>

We were planning on making a release last year but other things got in
the way. When time permits then we will make a full release. Snap shots
are easy for us to do and will do them when anything major changes or
when there is a serious bug.

> Is there anybody who is working on subversion support
> macros? (similar to cvs.emf)
>

Again, been thinking about it but not had time to set up a subversion
system and work out what needs to be done to support it. We would always
encourage other people to have a go if they have time.

Regards
Jon.

>
> Thanks for your good work,
> Ferenc Deak
>

Hi,

There are some references for the 'User Setup' tool with its old
location, the help menu instead of the new location, the Tools menu.
The affected files are

mail.emf
vm.emf
newuser.emf
me.ehf

I don't send a patch because searching for 'User Setup' and fixing these
lines is perhaps easier then verifying a patch

Regards,
feco

Deak, Ferenc wrote:
> Hi,
>
> In tcl the right keyword for an ''if' after an 'else' is
> 'elseif', so in tcl.eaf the line:
>
> elif "elsif {\p} {\r\r}\P"  "  elif"
> should be:
> elif "elseif {\p} {\r\r}\P"  "  elif"
>

Fixed.

Thanks
Jon.

> and my questions:
>
> I'm using the 20090310 snapshot without any problem.
> Is there any plan to release a newer snapshot to test, or
> even a new release?
>
> Is there anybody who is working on subversion support
> macros? (similar to cvs.emf)
>
>
> Thanks for your good work,
> Ferenc Deak
>

Hi,

There are some references for the 'User Setup' tool with its old
location, the help menu instead of the new location, the Tools menu.
The affected files are

mail.emf
vm.emf
newuser.emf
me.ehf

I don't send a patch because searching for 'User Setup' and fixing these
lines is perhaps easier then verifying a patch

Regards,
feco

 

Hi,

I wanted to write a function to copy the path and filename of the currently-open file.  (In termcap or console mode, I could copy at least the visible part of the filename to the clipboard by selecting the text in the modeline.  But, I couldn't figure out how to do it in the GUI version.)

I came up with this hack (below), which works.  (BTW I'm using ME 2006/09/09.)

;------------------------------------------------------------

; copy-filename: copy file name to clipboard

; (copies entire path + filename)

;------------------------------------------------------------

define-macro copy-filename

    set-variable #l0 $buffer-fname

    1 find-buffer "*copy-filename*"

    set-mark

    insert-string #l0

    end-of-line

    kill-region  ; copies to clipboard

    delete-buffer "*copy-filename*"

!emacro

In writing this, I had some trouble with find-buffer.

I wanted the switch to the buffer and the paste/kill actions not to be seen by the user.

A "hidden" buffer sounded like just the ticket.

The manpage says if the param to find-buffer is negative, the buffer is "hidden". 

And then it also says if bit 0x8 is set, the buffer is hidden.

So there might be a docsbug here.

Also, when I tried both of these things (individually and together) they caused my code not to work. Values -1, -8, -9 caused errors outright, and 9 caused it not to switch buffers.

And it turns out the buffer switch isn't visible after all, so leaving it as "1" seems to be okay.

Thanks

-Th

--
Thomas Hundt <tom@...> +1-415-867-6698

I've port one vgrep emf
-----
; -!- emf -!-
; Created:     Jul 18 2oo8
; Synopsis:    "vgrep" command handling
; Authors:     Lechee.Lai
;
define-macro vlist
     set-variable #l0 &cat $home "fte.grp"
     view-file #l0
     set-position "\x88"
     goto-line 1
     set-variable #l0 @wl
     !if &seq &lef #l0 5 "File:"
         ml-write "Vaild GRP format :-) C-j for selection"
     !else
         ml-write "Invaild GRP"
         !force 0 delete-buffer "fte.grp"
         !return
     !endif
     goto-position "\x88"
     buffer-init-hooks
!emacro

define-macro vgrep
     !if &inw @wc
         set-variable #l0 $window-col
         forward-char
         backward-word
         set-variable #l1 $window-col
         forward-word
         set-variable .osd.pat-cur &mid @wl #l1 &sub $window-col #l1
         set-variable $window-col #l0
     !else
         set-variable .osd.pat-cur ""
     !endif

     set-variable #l0 @ml1 "Search" .osd.pat-cur
     !if &less &len #l0 1
         ml-write "Cancel!"
         !return
     !endif
     !if &xse $buffer-fname ".*\\.c"
    	 set-variable #l5 "*.[ch]"
     !else
         !if &seq &set #l3 $buffer-fname ""
             set-variable #l3 $buffer-bname
         !endif
         !if &gre &set #l6 &rsin "." #l3 1
             set-variable #l4 &lef #l3 &sub #l6 1
             set-variable #l5 &rig #l3 &sub #l6 1
             set-variable #l5 &cat "*" #l5
         !else
             set-variable #l4 #l3
             set-variable #l5 "*"
         !endif
     !endif
     set-variable #l2 @ml01 "Dir"
     set-variable #l1 @ml1 "Mask" #l5
     !force 0 find-buffer "fte.grp"
     !if $status
         !force 0 delete-buffer "fte.grp"
     !endif
     pipe-shell-command &spr "vgrep --grep %s %s \\%s i" #l0 #l2 #l1
     delete-buffer "*command*"
     delete-window "*command*"
     ml-write "F11 for vlist -- C-j for pickup"
!emacro
---------
is there any possible using ENTER instead C-j

Thanks
Lechee

 

I've port one vgrep emf
-----
; -!- emf -!-
; Created: Jul 18 2oo8
; Synopsis: "vgrep" command handling
; Authors: Lechee.Lai
;
define-macro vlist
set-variable #l0 &cat $home "fte.grp"
view-file #l0
set-position "\x88"
goto-line 1
set-variable #l0 @wl
!if &seq &lef #l0 5 "File:"
ml-write "Vaild GRP format :-) C-j for selection"
!else
ml-write "Invaild GRP"
!force 0 delete-buffer "fte.grp"
!return
!endif
goto-position "\x88"
buffer-init-hooks
!emacro

define-macro vgrep
!if &inw @wc
set-variable #l0 $window-col
forward-char
backward-word
set-variable #l1 $window-col
forward-word
set-variable .osd.pat-cur &mid @wl #l1 &sub $window-col #l1
set-variable $window-col #l0
!else
set-variable .osd.pat-cur ""
!endif

set-variable #l0 @ml1 "Search" .osd.pat-cur
!if &less &len #l0 1
ml-write "Cancel!"
!return
!endif
!if &xse $buffer-fname ".*\\.c"
set-variable #l5 "*.[ch]"
!else
!if &seq &set #l3 $buffer-fname ""
set-variable #l3 $buffer-bname
!endif
!if &gre &set #l6 &rsin "." #l3 1
set-variable #l4 &lef #l3 &sub #l6 1
set-variable #l5 &rig #l3 &sub #l6 1
set-variable #l5 &cat "*" #l5
!else
set-variable #l4 #l3
set-variable #l5 "*"
!endif
!endif
set-variable #l2 @ml01 "Dir"
set-variable #l1 @ml1 "Mask" #l5
!force 0 find-buffer "fte.grp"
!if $status
!force 0 delete-buffer "fte.grp"
!endif
pipe-shell-command &spr "vgrep --grep %s %s \\%s i" #l0 #l2 #l1
delete-buffer "*command*"
delete-window "*command*"
ml-write "F11 for vlist -- C-j for pickup"
!emacro
---------
is there any possible using ENTER instead C-j

Thanks
Lechee

 

Oh, yeah, I've had problems with the buffers before, just as you describe... mind you I haven't extensively tested that bit of code, just came up with it this afternoon.  Will try some more, tomorrow.  (Yeah, set-position, I've used that before, too...)

Does @y copy things to the clipboard??

Mine complains, "Cannot set variable @y".  

Guess it's time to upgrade.  I've been waiting for an official release ;-)

Thanks!

-Tom

On Mon, Jul 20, 2009 at 6:40 PM, Steven Phillips <bill@jasspa.com> wrote:

Tom,

Playing with temp buffers is always tricky to get right, the typical worst case is if the current buffer (before to run your macro) is displayed in more than one window, in which case simply deleting the temp buffer  (or hiding it) wont work properly as the replacement buffer chosen will not be the original buffer as its already displayed (this then tends to break other macros which use your macro and strange things start to happen). Best to avoid temp buffers if you can and the version below does and should work in your version:

define-macro copy-filename
    set-variable @y $buffer-fname
!emacro

For backward compatibility reasons an arg of -1 to find-buffer is converted to 0x8 and an arg of <-1 (e.g. -8 or -9) is converted to 0x18 this was done when additions like bit 0x04 were made, bit 0x10 forces the hiding of all instances of the given buffer , so:

     0x18 find-buffer "*copy-filename*"

Really should work (in my version, yours may not have bit 0x10) but hunter through the macros I can't find a single use (probably because of the double window problem mentioned above) so I would stick to the non-temp buffer approach or start researching set-position!

Steve

Tom Hundt wrote:

 

Hi,

I wanted to write a function to copy the path and filename of the currently-open file.  (In termcap or console mode, I could copy at least the visible part of the filename to the clipboard by selecting the text in the modeline.  But, I couldn't figure out how to do it in the GUI version.)

I came up with this hack (below), which works.  (BTW I'm using ME 2006/09/09.)

;------------------------------------------------------------

; copy-filename: copy file name to clipboard

; (copies entire path + filename)

;------------------------------------------------------------

define-macro copy-filename

    set-variable #l0 $buffer-fname

    1 find-buffer "*copy-filename*"

    set-mark

    insert-string #l0

    end-of-line

    kill-region  ; copies to clipboard

    delete-buffer "*copy-filename*"

!emacro

In writing this, I had some trouble with find-buffer.

I wanted the switch to the buffer and the paste/kill actions not to be seen by the user.

A "hidden" buffer sounded like just the ticket.

The manpage says if the param to find-buffer is negative, the buffer is "hidden". 

And then it also says if bit 0x8 is set, the buffer is hidden.

So there might be a docsbug here.

Also, when I tried both of these things (individually and together) they caused my code not to work. Values -1, -8, -9 caused errors outright, and 9 caused it not to switch buffers.

And it turns out the buffer switch isn't visible after all, so leaving it as "1" seems to be okay.

Thanks

-Th

--
Thomas Hundt <tom@...> +1-415-867-6698

--
Thomas Hundt <tom@...> +1-415-867-6698

Is there going to be a new release of MicroEmacs? Looking, it seems the last
release was in 2006?

Jeremy

cp200205 wrote:
> Is there going to be a new release of MicroEmacs? Looking, it seems the last
release was in 2006?
>
> Jeremy
>
>
>

Hi Jeremy,

There will be when we get some time. At the moment we do not have that
much time to do it, a release cycle will typically take us 1-2 months
and neither of us have that much time available at the moment. Sounds a
little lame because it has been 3 years, but have been busy for 3 years!

We dropped a development snapshot here some time ago:

http://www.jasspa.com/development/

which is mainly a few minor bug fixes and some extended features such as
built in grep and find (i.e. do not need external program) which is
pretty handy. There is nothing wrong with this release as far as we know
and is solid. There is a pre-built windows binary, source and the macros.

The only thing that is preventing us from making a new release is the
outstanding documentation items. As soon as we find time to bring the
documentation up to date then we will be able to make a new release and
issue. Maybe we should not be so strict as to require that the
documentation should match the release; but that is just the way that we
are and until everything is fully consistent then we will not make that
final release.

So by all means move over to the development binaries/source it is
stable for everyday use (and is what we are using).

Regards
Jon.

A Beta version of MicroEmacs 2009 has been uploaded to

http://www.jasspa.com/release_20090909

This also includes a new Windows installer setup.exe.
Any problems then please let us know.

Regards
Jon.