On 11-10-31 01:19 PM, Jon Green wrote:
>
> On 31/10/2011 15:07, Reza Roboubi wrote:
> > On 11-10-31 06:11 AM, Jon Green wrote:
> > > If you are able to send some code that reproduces the issue then
> > that would be useful.
> > >
> >
> > Okay, the attached file will narrow it down pretty nicely. Line 52 must
> > be scrolled to the top of the page and then the highlighting is wrong.
> > This is the version information and buffer mode is a standard .c file:
> Hi Reza,
>
> The issue is the look-back length in the template file. In the file
> scenario
> that you have posted then by scrolling to line 52 then the
> highlighting is
> expected to look back more than 50 lines in order to find an anchor
> point on
> which to base its highlighting scheme for the current line.
>
> If you look at hkc.emf which performs the highlighting then the
> template is
> defined with a 50 line look back at line 110 i.e.
>
> ; Hi-light C Mode
> 0 hilight .hilight.c 2 50
>

Thank you Jon.  First, the problem is that the quotes are escaped.
Without the escapes everything works.  In this simple case, the easy
work-around is to put such comments inside separate "README" files.

The "hilight 150" look-back feature isn't _really_ for handling this
problem, but rather, the "50" is the "largest comment size possible" in
case that you are actually starting _inside_ a comment already.

Eventually (if not too messy) it would be great to modify hilight to be
globally precise and complete:  hilight only needs to mark, globally and
persistently, per-buffer, approximately every 40 lines or 400 characters
or so.  The marking says:  "This Line Or Character lies outside any
bracketed region."

With markings like that we can _completely_ eliminate hilight's
"look-back" parameter.  The user never even needs to know about hilight
look-backs.

That way hilight can even scale to ridiculously huge files (for example
preprocessed output or whatever else.)

Reza.

On 31 Oct 2011, at 21:33, Reza Roboubi <reza@...> wrote:

> On 11-10-31 01:19 PM, Jon Green wrote:
>>
>> On 31/10/2011 15:07, Reza Roboubi wrote:
>>> On 11-10-31 06:11 AM, Jon Green wrote:
>>>> If you are able to send some code that reproduces the issue then
>>> that would be useful.
>>>>
>>>
>>> Okay, the attached file will narrow it down pretty nicely. Line 52 must
>>> be scrolled to the top of the page and then the highlighting is wrong.
>>> This is the version information and buffer mode is a standard .c file:
>> Hi Reza,
>>
>> The issue is the look-back length in the template file. In the file
>> scenario
>> that you have posted then by scrolling to line 52 then the
>> highlighting is
>> expected to look back more than 50 lines in order to find an anchor
>> point on
>> which to base its highlighting scheme for the current line.
>>
>> If you look at hkc.emf which performs the highlighting then the
>> template is
>> defined with a 50 line look back at line 110 i.e.
>>
>> ; Hi-light C Mode
>> 0 hilight .hilight.c 2 50
>>
>
> Thank you Jon.  First, the problem is that the quotes are escaped.
> Without the escapes everything works.  In this simple case, the easy
> work-around is to put such comments inside separate "README" files.
>
> The "hilight 150" look-back feature isn't _really_ for handling this
> problem, but rather, the "50" is the "largest comment size possible" in
> case that you are actually starting _inside_ a comment already.
>
> Eventually (if not too messy) it would be great to modify hilight to be
> globally precise and complete:  hilight only needs to mark, globally and
> persistently, per-buffer, approximately every 40 lines or 400 characters
> or so.  The marking says:  "This Line Or Character lies outside any
> bracketed region."
>
> With markings like that we can _completely_ eliminate hilight's
> "look-back" parameter.  The user never even needs to know about hilight
> look-backs.
>
> That way hilight can even scale to ridiculously huge files (for example
> preprocessed output or whatever else.)
>
> Reza.
>
>


Hi Reza,

I do not quite agree with your analysis because the quotes are fine in the
comment when the current position is less than the look-back distance away. If
the quotes in the comment were generally a problem then you would expect this to
cause a problem irrespective of the actual distance of the offending statement
away from the comment.

You can check out it is the look back length by changing the value to 51 and the
bad highlighting is then ok. Then insert a new line into ooo.c before the
statement and scroll up the window then the highlight anomaly returns. You can
repeat this a few times by changing the look back and then line position.

So I would not expect that you should be forced to re-organise your codebase by
taking some drastic action to separate out some of the code because of the
editor you use.

There are a lot of look back sizes in the template file for the various
hilighting schemes, including comments. I think we should parameterise these
values so that it is much easier to increase them all in one go rather than
using constants. 50 is a little small these days, especially for some of the
public domain software with large version histories and licenses contained, with
the current processing power available the longer look back does not really
become noticeable.

As for your idea of putting down anchors, this has potential benefits, I am not
sure if this completely eradicates look back in its entirety because it must
still be performed for brackets in lines.

Regards
Jon.



> ------------------------------------
>
> __________________________________________________________________________
>
> 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
>
>
>

Hi Jon,

On 11-10-31 03:54 PM, Jon Green wrote:
>
> I do not quite agree with your analysis because the quotes are fine in
> the comment when the current position is less than the look-back
> distance away. If the quotes in the comment were generally a problem
> then you would expect this to cause a problem irrespective of the
> actual distance of the offending statement away from the comment.
>
The question isn't what the problem is.  The question is, what's the
solution?  We both agree that changing the look-back length _only_
solves this issue if we set look-back >= file-line-number.  That's a fact.
>
> As for your idea of putting down anchors, this has potential benefits,
> I am not sure if this completely eradicates look back in its entirety
> because it must still be performed for brackets in lines.
>
Yes, hilight will simply have to look back until it finds the first
anchor outside of the window's view port.  That way, you get global and
scalable highlighting, for any language or file size.  And I suspect
it's pretty easy to do:  Could someone who knows the source code well
give clear instructions of what needs to change and the potential
pitfalls to watch for?

Reza.

I'm very sorry for the stupid formatting of my last email.  The line
spaces were all broken:

On 11-10-31 04:40 PM, Reza Roboubi wrote:
> Hi Jon,
>
> On 11-10-31 03:54 PM, Jon Green wrote:
>>
>> I do not quite agree with your analysis because the quotes are fine
>> in the comment when the current position is less than the look-back
>> distance away. If the quotes in the comment were generally a problem
>> then you would expect this to cause a problem irrespective of the
>> actual distance of the offending statement away from the comment.
>>

> The question isn't what the problem is.  The question is, what's the
> solution?  We both agree that changing the look-back length _only_
> solves this issue if we set look-back >= file-line-number.  That's a
> fact.

>> As for your idea of putting down anchors, this has potential
>> benefits, I am not sure if this completely eradicates look back in
>> its entirety because it must still be performed for brackets in lines.
>>

> Yes, hilight will simply have to look back until it finds the first
> anchor outside of the window's view port.  That way, you get global
> and scalable highlighting, for any language or file size.  And I
> suspect it's pretty easy to do:  Could someone who knows the source
> code well give clear instructions of what needs to change and the
> potential pitfalls to watch for?
>
> Reza.

Hi all

Has anyone else noticed any problems with the latest jasspa me version
not using or reading session files ??

I updated to use the new version about a month ago and immediately
noticed the latest version did not correctly read/use the previous
version session files
(regenerate the previous session) and does not correctly read/use
session files made from a new changed session done within itself..

The session files seem to have the correct ( new session ) info - file
names at least and the startup status line message indicate the session
has been read ( but files not loaded....)

??

--
-- hops

------ Original Message ------
From: "Jeremy Cowgar" <jeremy@...>
To: "Group, MicroEmacs User" <jasspa@yahoogroups.com>
Sent: 11/26/2011 11:05:38 AM
Subject: [jasspa] New files, create as CR only on Windows, not CR&LF
>
>I have went to my user configuration and removed the "Lf" flag, but
>new files still seem to be created as CRLF, not just CR. Am I doing
>something wrong?


I was able to add

-1 global-mode "lf"

to my startup file and that seems to have done it.

Jeremy

 

Hi all

Has anyone else noticed any problems with the latest jasspa me version
not using or reading session files ??

I updated to use the new version about a month ago and immediately
noticed the latest version did not correctly read/use the previous
version session files
(regenerate the previous session) and does not correctly read/use
session files made from a new changed session done within itself..

The session files seem to have the correct ( new session ) info - file
names at least and the startup status line message indicate the session
has been read ( but files not loaded....)

??

--
-- hops

 

------ Original Message ------
From: "Jeremy Cowgar" <jeremy@...>
To: "Group, MicroEmacs User" <jasspa@yahoogroups.com>
Sent: 11/26/2011 11:05:38 AM
Subject: [jasspa] New files, create as CR only on Windows, not CR&LF
>
>I have went to my user configuration and removed the "Lf" flag, but
>new files still seem to be created as CRLF, not just CR. Am I doing
>something wrong?


I was able to add

-1 global-mode "lf"

to my startup file and that seems to have done it.

Jeremy

 

Not sure how you had removed the 'lf' mode but global-mode is the right way to go for a global change, alternatively consider creating a my<file-type>.emf hook to change just one file type.

Note that if you have 'auto' mode still enabled lf mode will still be enabled for old files that have lf chars in their end of line format.

Steve

Jeremy Cowgar wrote:

 

------ Original Message ------
From: "Jeremy Cowgar" <jeremy@...>
To: "Group, MicroEmacs User" <jasspa@yahoogroups.com>
Sent: 11/26/2011 11:05:38 AM
Subject: [jasspa] New files, create as CR only on Windows, not CR&LF
>
>I have went to my user configuration and removed the "Lf" flag, but
>new files still seem to be created as CRLF, not just CR. Am I doing
>something wrong?


I was able to add

-1 global-mode "lf"

to my startup file and that seems to have done it.

Jeremy

 

Tools > User Setup > General > Show Modes. lf is listed, there I "unchecked" it.

 

Jeremy

------ Original Message ------
From: "Steven Phillips" <bill@...>
To: jasspa@yahoogroups.com
Sent: 11/29/2011 1:48:45 PM
Subject: Re: [jasspa] New files, create as CR only on Windows, not CR&LF

 

Not sure how you had removed the 'lf' mode but global-mode is the right way to go for a global change, alternatively consider creating a my<file-type>.emf hook to change just one file type.

Note that if you have 'auto' mode still enabled lf mode will still be enabled for old files that have lf chars in their end of line format.

Steve

Jeremy Cowgar wrote:

 

------ Original Message ------
From: "Jeremy Cowgar" <jeremy@...>
To: "Group, MicroEmacs User" <jasspa@yahoogroups.com>
Sent: 11/26/2011 11:05:38 AM
Subject: [jasspa] New files, create as CR only on Windows, not CR&LF
>
>I have went to my user configuration and removed the "Lf" flag, but
>new files still seem to be created as CRLF, not just CR. Am I doing
>something wrong?


I was able to add

-1 global-mode "lf"

to my startup file and that seems to have done it.

Jeremy

On 11/30/2011 7:42 AM, Steven Phillips wrote:
> Are the files local?

Yes they're local
/Documents and Settings/hops/Application Data/JASSPA/hops.esf

ME does not read network files in as the network
> may not be available in which case ME will hang for a long time (there's
> probably a way of making it though....).
Its not hanging at all. Starts up as normal
The status line message indicates that its read the session file
'[Session read]' but a session with the files is is not recreated


>
Was there any change to the session file format at the last version
( this is on Windows XP)

> Are there any other symptoms as I've not had any problems myself.
Pox.

Thats pretty much it no session (re)made but looks like the macro code
is passing through the reading of the session file


I just tried manually saving and manually loading the session file
('save-session' and 'read-session') and that seemed to work.

Stopping and restarting after that me-10 still didnt automatically load
the session on startup (in spite of the shown '[Session read]' showing
but if I run a 'read-session' command manually it does load the sessions
files.

In a default distribution where in the macro files run on startup is the
session loaded ( read-session command run)?

>
> Steve
>
> hops wrote:
>>
>>
>> Hi all
>>
>> Has anyone else noticed any problems with the latest jasspa me version
>> not using or reading session files ??
>>
>> I updated to use the new version about a month ago and immediately
>> noticed the latest version did not correctly read/use the previous
>> version session files
>> (regenerate the previous session) and does not correctly read/use
>> session files made from a new changed session done within itself..
>>
>> The session files seem to have the correct ( new session ) info - file
>> names at least and the startup status line message indicate the session
>> has been read ( but files not loaded....)
>>
>> ??
>>
>> --
>> -- hops
>>
>>
>


--
-- hops

so there isn't a softwrap feature?

it could be interesting if we can compile lua (embed) it in as a extension
language, while at the same time keep the current macro system....

just some thought

--- In jasspa@yahoogroups.com, "isaacpei" <isaacpei@...> wrote:
>
> thanks, Tom
> yes, yours best explained what I am looking for. thanks!
>
> --- In jasspa@yahoogroups.com, Tom Hundt <thundt@> wrote:
> >
> > org mode is a mode for GNU Emacs that supports outines, checklists, etc.
> > http://orgmode.org/
> >
> > I've played around with it and wish MicroEmacs had it.  I've gone so far as
> > to have both ME and Gnu installed just to support some to-do lists.  I'm
> > Lisp-challenged, however, and that always stops me from switching over.
> >
> > I think "soft wrap" means wrapping long lines by setting an editor flag, not
> > by inserting actual linefeeds into the text.  What Notepad does in Windows.
> > http://www.gnu.org/software/libtool/manual/emacs/Longlines.html
> >
> > -Tom
> >
> >
> > On Mon, Jul 18, 2011 at 12:45 PM, Steven Phillips <bill@> wrote:
> >
> > > **
> > >
> > >
> > > Isaac,
> > >
> > > Welcome to the group!
> > >
> > > Sorry but I'm not familiar with the terms softwrap or orgmode - what are
> > > they?
> > >
> > > I'd guess that softwrap is the wrapping of long lines in the display so
all
> > > the text is visible? If so the answer is no (there has to be some reason
why
> > > this is 'micro' emacs!)
> > >
> > > Steve
> > >
> > >
> > > isaacpei wrote:
> > >
> > >
> > >
> > > Hello,
> > >
> > > I am an new user of microemacs, I have
> > > two specific questions:
> > > 1. is there a softwrap feature in uemacs?
> > > 2. is there the 'orgmode' in uemacs?
> > >
> > > thanks a lot!
> > >
> > > Best regards,
> > > Isaac
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > --
> > Thomas Hundt <tom@> +1-415-867-6698
> >
>

Hello,

I tried to use foldable Bash functions. Item list is working but folding not.

example shell-file example.sh:

function echoerr {
    echo "$@" 1>&2;
}


Here is myshell.emf

; adding an f to the original setup-mask (for folding, collapse)
set-variable .fhook-shell.setup-mask "aefghikmoptux"

set-variable .fhook-shell.collapse-open  "^function"
set-variable .fhook-shell.collapse-close "^}"
set-variable .fhook-shell.collapse-mclose "1"
set-variable .fhook-shell.collapse-mnext "-1"


set-variable .fhook-shell.item-list-s1 "^function \\(\\w+\\)"
set-variable .fhook-shell.item-list-r1 "Func \ecB\\1\ecA"

;Any ideas to get folding support in bash-files?
; regards,
; Detlef

Hi Detlef,

Your myshell.emf is fine.  The problem is that your folding state is
saved in the registry and you need to enable it now that you have
changed the mode, by default this is turned off because you have added a
new mode.

  From within a .sh buffer (i.e. when editing file example.sh) then do

M-x major-mode-setup

Check the "Setup Folding"box. Then it should all be working,

Regards
Jon.

On 13/03/2012 11:58, Dr. Detlef wrote:
> Hello,
>
> I tried to use foldable Bash functions. Item list is working but folding not.
>
> example shell-file example.sh:
>
> function echoerr {
>     echo "$@" 1>&2;
> }
>
>
> Here is myshell.emf
>
> ; adding an f to the original setup-mask (for folding, collapse)
> set-variable .fhook-shell.setup-mask "aefghikmoptux"
>
> set-variable .fhook-shell.collapse-open  "^function"
> set-variable .fhook-shell.collapse-close "^}"
> set-variable .fhook-shell.collapse-mclose "1"
> set-variable .fhook-shell.collapse-mnext "-1"
>
>
> set-variable .fhook-shell.item-list-s1 "^function \\(\\w+\\)"
> set-variable .fhook-shell.item-list-r1 "Func \ecB\\1\ecA"
>
> ;Any ideas to get folding support in bash-files?
> ; regards,
> ; Detlef
>

Indeed "major-mode-setup" solved the problem with the old registry setting.

Thanks Jon.

regards,
Detlef

--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> Hi Detlef,
>
> Your myshell.emf is fine.  The problem is that your folding state is
> saved in the registry and you need to enable it now that you have
> changed the mode, by default this is turned off because you have added a
> new mode.
>
>  From within a .sh buffer (i.e. when editing file example.sh) then do
>
> M-x major-mode-setup
>
> Check the "Setup Folding"box. Then it should all be working,
>
> Regards
> Jon.
>
> On 13/03/2012 11:58, Dr. Detlef wrote:
> > Hello,
> >
> > I tried to use foldable Bash functions. Item list is working but folding
not.
> >
> > example shell-file example.sh:
> >
> > function echoerr {
> >     echo "$@" 1>&2;
> > }
> >
> >
> > Here is myshell.emf
> >
> > ; adding an f to the original setup-mask (for folding, collapse)
> > set-variable .fhook-shell.setup-mask "aefghikmoptux"
> >
> > set-variable .fhook-shell.collapse-open  "^function"
> > set-variable .fhook-shell.collapse-close "^}"
> > set-variable .fhook-shell.collapse-mclose "1"
> > set-variable .fhook-shell.collapse-mnext "-1"
> >
> >
> > set-variable .fhook-shell.item-list-s1 "^function \\(\\w+\\)"
> > set-variable .fhook-shell.item-list-r1 "Func \ecB\\1\ecA"
> >
> > ;Any ideas to get folding support in bash-files?
> > ; regards,
> > ; Detlef
> >
>

Hi Jon,
Long time, no new jasspa emacs news .. :-). I was wondering if you have any new
stuff to put my hands on ??.

New features into ME..??

Kind Regards
Pedro

Hi Pedro,

Always seem to be busy these days with other things.
Steve has made a few fixes and there's now a new SVN client (which I have not
tried yet).
You are right we ought to bundle it up and refresh it again.
I'll try and find some time.

If there are any more contributions then feel free to send them to us and I will
try and do a 2012 release sometime.

Regards
Jon.


On 24 Apr 2012, at 12:56, "azynheira" <azynheira@...> wrote:

> Hi Jon,
> Long time, no new jasspa emacs news .. :-). I was wondering if you have any
new stuff to put my hands on ??.
>
> New features into ME..??
>
> Kind Regards
> Pedro
>
>
>
> ------------------------------------
>
> __________________________________________________________________________
>
> 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
>
>
>

Hi Guys,
My point was not even to have a fully fledged release but something (beta,alpha,
...), we in "general population" can use and report bugs against :-)

Since in my new job we are using Git and it's also getting popular, I was
thinking in implementing a Git client for ME. Will provide it to you once it
does something relevant.

Kind Regards,
Pedro



--- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
>
> Hi Pedro,
>
> Always seem to be busy these days with other things.
> Steve has made a few fixes and there's now a new SVN client (which I have not
tried yet).
> You are right we ought to bundle it up and refresh it again.
> I'll try and find some time.
>
> If there are any more contributions then feel free to send them to us and I
will try and do a 2012 release sometime.
>
> Regards
> Jon.
>
>
> On 24 Apr 2012, at 12:56, "azynheira" <azynheira@...> wrote:
>
> > Hi Jon,
> > Long time, no new jasspa emacs news .. :-). I was wondering if you have any
new stuff to put my hands on ??.
> >
> > New features into ME..??
> >
> > Kind Regards
> > Pedro
> >
> >
> >
> > ------------------------------------
> >
> > __________________________________________________________________________
> >
> > 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
> >
> >
> >
>

I have installed JASSPA MicroEmacs'09 on Windows XP and JASSPA MicroEmacs'06 on
DOS. I'm very pleased with how the program runs and looks. It is fantastic
considering its overall size. However, I'm at a loss as to enabling bookmarks to
be restored from a previous session. I've read about User Profiles, the -c
option, save-session, etc., set MENAME and MEUSERPATH in autoexec.bat, run the
save-session and read-session commands etc., however nothing works to save
booksmarks from session to session. Can anyone help point me in the right
direction or offer any tips?

On 04/05/2012 20:30, williamjgiberson wrote:
> I have installed JASSPA MicroEmacs'09 on Windows XP and JASSPA MicroEmacs'06
on DOS. I'm very pleased with how the program runs and looks. It is fantastic
considering its overall size. However, I'm at a loss as to enabling bookmarks to
be restored from a previous session. I've read about User Profiles, the -c
option, save-session, etc., set MENAME and MEUSERPATH in autoexec.bat, run the
save-session and read-session commands etc., however nothing works to save
booksmarks from session to session. Can anyone help point me in the right
direction or offer any tips?
>
>

Hi William?,

I am not sure what you mean by bookmarks. I think possibly you mean
"alpha-marks". These are not saved in the session.

What is saved in a session is described in the help page read-session(3) and
includes:

- Searching and replacing history.
- Buffer name history.
- Command name history.
- File name history.
- General (all the rest) history.
- Buffer and file list with line numbers.

So by saving and restoring the session then all of the buffers that were
previously loaded are restored at their existing line number, history for
search/replace, file names, shell history etc. is saved.

So starting the editor with -c i.e. "me -c" will basically restore you back to
where you were when you previously quit the editor. Transient information like
temporary highlighting, alpha marks etc. is not saved/restored in the session,
this is the bit I think you are referring to.

So typically one would try to always start with "me -c" from the command line
if you wanted to keep all of the files etc. from the previous session. In a
window manager environment then the start command is typically "me -o -c %F"
where %F is the file name which would come from the window manager (use
appropriate syntax in the place of %F for the file manager you are using). You
quit the editor as normal and do not need to do anything special.

Other than that I am afraid to say that we cannot satisfy your requirements for
"bookmarks" at the moment - Sorry!

Regards
Jon.

On 04/05/2012 20:30, williamjgiberson wrote:
> I have installed JASSPA MicroEmacs'09 on Windows XP and JASSPA MicroEmacs'06
on DOS. I'm
very pleased with how the program runs and looks. It is fantastic considering
its overall
size. However, I'm at a loss as to enabling bookmarks to be restored from a
previous
session. I've read about User Profiles, the -c option, save-session, etc., set
MENAME and
MEUSERPATH in autoexec.bat, run the save-session and read-session commands etc.,
however
nothing works to save booksmarks from session to session. Can anyone help point
me in the
right direction or offer any tips?
>
>

On 04/05/2012 21:52, Jon Green wrote:
Hi William?,

>I am not sure what you mean by bookmarks. I think possibly you mean
"alpha-marks". These are not saved in the session.

What is saved in a session is described in the help page read-session(3) and
includes:

- Searching and replacing history.
- Buffer name history.
- Command name history.
- File name history.
- General (all the rest) history.
- Buffer and file list with line numbers.

So by saving and restoring the session then all of the buffers that were
previously loaded are restored at their existing line number, history for
search/replace, file names, shell history etc. is saved.

So starting the editor with -c i.e. "me -c" will basically restore you back to
where you were when you previously quit the editor. Transient information like
temporary highlighting, alpha marks etc. is not saved/restored in the session,
this is the bit I think you are referring to.

So typically one would try to always start with "me -c" from the command line
if you wanted to keep all of the files etc. from the previous session. In a
window manager environment then the start command is typically "me -o -c %F"
where %F is the file name which would come from the window manager (use
appropriate syntax in the place of %F for the file manager you are using). You
quit the editor as normal and do not need to do anything special.

Other than that I am afraid to say that we cannot satisfy your requirements for
"bookmarks" at the moment - Sorry!

Regards
Jon.
>
>

Hi Jon,

Thank you very much for the timely, helpful, clear and concise response to my
message. You are correct that I was referring to "alpha-marks". I had
"bookmarks" on the brain from working with GNU Emacs and also because the menu
bar 'search' menu of JASSPA MicroEmacs'09 uses "Set Bookmark" and "Goto
Bookmark" as menu item titles. Anyway, because I now know that alpha-marks are
not saved in a session, I'll see if I can make use of "Incremental Search C-s"
for moving to the various section heading titles of my 1BigFile.txt file that I
keep.

Respectfully,
William

 

On 04/05/2012 20:30, williamjgiberson wrote:
> I have installed JASSPA MicroEmacs'09 on Windows XP and JASSPA MicroEmacs'06 on DOS. I'm very pleased with how the program runs and looks. It is fantastic considering its overall size. However, I'm at a loss as to enabling bookmarks to be restored from a previous session. I've read about User Profiles, the -c option, save-session, etc., set MENAME and MEUSERPATH in autoexec.bat, run the save-session and read-session commands etc., however nothing works to save booksmarks from session to session. Can anyone help point me in the right direction or offer any tips?
>
>

Hi William?,

I am not sure what you mean by bookmarks. I think possibly you mean
"alpha-marks". These are not saved in the session.

What is saved in a session is described in the help page read-session(3) and
includes:

- Searching and replacing history.
- Buffer name history.
- Command name history.
- File name history.
- General (all the rest) history.
- Buffer and file list with line numbers.

So by saving and restoring the session then all of the buffers that were
previously loaded are restored at their existing line number, history for
search/replace, file names, shell history etc. is saved.

So starting the editor with -c i.e. "me -c" will basically restore you back to
where you were when you previously quit the editor. Transient information like
temporary highlighting, alpha marks etc. is not saved/restored in the session,
this is the bit I think you are referring to.

So typically one would try to always start with "me -c" from the command line
if you wanted to keep all of the files etc. from the previous session. In a
window manager environment then the start command is typically "me -o -c %F"
where %F is the file name which would come from the window manager (use
appropriate syntax in the place of %F for the file manager you are using). You
quit the editor as normal and do not need to do anything special.

Other than that I am afraid to say that we cannot satisfy your requirements for
"bookmarks" at the moment - Sorry!

Regards
Jon.

Hi Steve,

After receiving your message I continued to look into my setup and I now have
me32 '09 working to my satisfaction on Windows XP. I discovered that me32 didn't
like to be installed in the "Program Files" directory because it wouldn't accept
the "-c" command line option for that path. I moved everything to C:\JASSPA and
all is well.

Thanks for the help - much appreciated. And thanks for such a nifty text editing
program!

William



> Steven Phillips wrote:
>
> Welcome William,
>
> Something did not ring true with Jon's response, I seemed to recall adding
this
> feature but its taken a while to track it down.
>
> Firstly 'Bookmarks' is a cosmetic pseudonym used in ME's GUIs which use the
> alpha-mark functions under the hood, not sure if we should have bothered  but
I
> guess the edit menu's 'Set Alpha mark' would not have meant much to most new
> users.
>
> Anyway, the saving of alpha/bookmarks must be enabled using the session-setup
> tool, this tool configures the current session - simply enable the 'Save
buffer
> bookmarks' option. As a side note, if the last 'Auto Update' option is
disabled
> then the session file is not automatically saved on exit so you can create
> 'static' sessions.
>
> Steve
>

List,

Is it possible to entirely disable justification (set it to 'none')
for all the Major modes by default?


Thank you,
Jerome

Hi Jerome,

I am afraid not because the default setting is built into each individual file
template (hkxxx.emf).

I must admit I do not really understand what what problem you are trying to
solve, as most files are conventionally left to right and only the formatted
text formats performs fully justified text against both margins, hence there has
never been a need to globally modify justification across all buffer modes.

Regards
Jon.

On 8 Feb 2013, at 23:19, Jerome Ibanes <jibanes@...> wrote:

> List,
>
> Is it possible to entirely disable justification (set it to 'none')
> for all the Major modes by default?
>
>
> Thank you,
> Jerome
>
>
> ------------------------------------
>
> __________________________________________________________________________
>
> 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

> I must admit I do not really understand what what problem you are trying to
solve, as most files are conventionally left to right and only the formatted
text formats performs fully justified text against both margins, hence there has
never been a need to globally modify justification across all buffer modes.

Thank you, I will try to clarify my request.

Other than using MicroEmacs for coding, I also use it to manage notes and
documentation. As it's usually the case with technical documentation, I often
paste in them some snippets of code or shell script, which often go beyond the
80 columns "limit".

Justification then kicks-in and reformats them, which is a major inconvenience
with (shell|python|perl|...) scripts.

Because my notes/documentation are usually kept in a '.txt' file, MicroEmacs
defaults to "Both Justify Mode" and I would like to make it default to "None
Justify Mode" without setting this manually. Could you please point me towards
the right way to address this?
I will set it explicitly should I want justification.

Thank you,
Jerome