@Joe Riel: Thanks for your concern.

I do have some experience with writing modules, achieving them (using march, etc.), and accessing their exports using the with-command (at top-level). And I do know how to access exports without the with-command using their full names. But, as I previously wrote, I have never before used the read command. As a first round of reorganization of my code, I will just use this read-command, suspending for the moment the achieving.

@Joe Riel: Thanks for that info. I decided not to pursue using Emacs because the installation procedure itself seemed somewhat daunting to me.

@Joe Riel: Thanks for an extensive reply, again. Having actually not tested it explicitly yesterday, I had a hunch that perhaps I was mistaken with respect to $include. So, I guess, it is down to the read or the with command (and perhaps the uses command). I think I will, at least for getting starting with the reorganization of my code, pursue using the read command as outlined in your second paragraph. Having to use full paths, will not be a big issue to me.

@Carl Love: I do not have any issues as such with the with command. But using the read command instead avoids archive management, as far as I understand it. You have a point, though, concerning the overwriting of commands, but it will play no role for me, as the procedures of mine will be constructed so that no conflict of names arises.

As an aside perhaps, what are the overall pros and cons concerning the commands read, include and with, respectively? I ask because to me it seems that the read and include commands perform pretty much the same thing, both processing the code of the file being read/included. Or am I mistaken?

And various modules and in them various procedures are fully accessible after having read/included the files, so libraries and thus the with command is thus not strictly needed. Or am I mistaken?

I guess that what I am asking for is some overall advice, from the experts here, as which structure to aim for when I am going to rebuild my Maple programming setup.

@Axel Vogt: Apart from minor issues, jEdit is now up and running with Maple syntax highlighting. Calling Maple's help pages seems not to be an option, however, and why should it be for such a third-party product.

I see your point, though, in case you had that in mind: Using jEdit will require running Maple alongside to be able to access it help pages. But that would be a minor issue for me, as in most circumstances, I think, I would have a Maple worksheet opened anyway.

@JohnS: Thanks for your suggestions regarding an editor. For the moment, though, I'm trying to make jEdit, as recommended by William Spaetzel, run properly.

@Axel Vogt: Thanks for that tip, a tip to which I will perhaps return; for the moment, though, I'm pursuing using an external editor.

@Axel Vogt: Do you mean Classic Worksheet? As far as I can figure out, Classic Worksheet is not supported under 64 bit (Windows 7).

@Joe Riel: I far as I recall, I have never used the read command; I have only used the with command.

But I have just written a simple test module in an external editor, saved it simply as an .mw-file, read it from within a Maple worksheet with the read-command, and loaded the resulting library with the with-command. And it works! As a positive surprise to me, the read command executes the code within the file being read, thereby automatically creating/updating the library file(s); of course, a command like march('create',"...") in the file can generally only be executed once.

Thanks for calming me down a bit.

@Joe Riel: Thanks for a quite extensive answer. I am afraid, though, that it is quite over my head, and that is not in any way meant reproachfully. Having programmed several packages of my own, I do have experience with how from within the standard Maple environment to make modules, and how from them to create libraries. But from what you write, this seems to be just a tiny amount of what is needed if I am to do it using an external editor.

To be honest, I feel quite lost now: With Microsoft phasing out updates for Windows XP as of April 2014, I have been forced to run Windows 7 (having also to buy a brand new computer). This in turn has forced me to update from Maple 9.5 to Maple 17, because 9.5 does run neither under 32 bit nor 64 bit of Windows 7. And this (quite to my surprise, as I thought the tabbing issue I stumbled upon in Maple 11 over three years ago had by now been resolved) has in practice made my Maple 9.5 documents uneditable.

But perhaps I am just tired now, it being better to sleep on it.

@Carl Love: Thanks for your suggestion. I have just tried it out a bit, writting a small piece of code. The highlighting and bracket mathing, besides the working tab-key, of course, is in fact quite nice. Perhaps the packages I have written for myself could be recast in Maple 17 using this environment. But a certain worksheet of mine, that uses some of these packages - the front end, so to speak - cannot, and it uses tabbing too.

On a side note, why on God's green Earth does MapleSoft choose(?) to throw out a working syntax-error-location when going from Maple 16 to Maple 17?

@Christopher2222: Thanks for your reply.

I wonder whether a wish list would have any effect, it being now more than three years ago that the tabbing-issue emerged with Maple 11. Why has it not been resolved, I ask myself. It cannot only be I that find it a clear-cut GUI-deficiency; other users must have found it a nuisance too, I guess.

Copy-pasting a few spaces in place of a single tab is not something I would be keen on being forced to use. For one thing, one would have to remember to 'refresh' the copy, if other code is copy-pasted. But thanks for suggesting it anyway.

No, I have not checked out the physics package yet. In fact I have not checked out very much, being occupied with getting the conversion of my Maple 9.5 documents, and thus my research related to them, up and running.

@Preben and Carl: Thanks for your replies. I have just tested some other Maple 9.5 documents of mine. The problem arises only for lines that have been indented using tabbing. This seems to be the very same issue that made me abandon Maple 11. This time, however, I have no choice: if I cannot get these Maple 9.5 documents up and running properly under Maple 17, then I am stuck, as there is no turning back to Windows XP and thus Maple 9.5.

Perhaps the problem is due to the fact (as just realized) that in Maple 17, code cannot, not even in 1D Math Input mode, be indented using the TAB-key; using this key, just makes the cursor jump to the following execution group. But how then can (larger amounts of) code be effectively indented to make it readable without, say, the silly use of repeated space bar? Any suggestions are welcome.

Thanks for your kindness, Brian Abraham.