Re: AUCTeX tool-bar and icons

* Ralf Angeli (2008-05-17) writes:

> * Reiner Steib (2008-05-15) writes:
>
>> On Thu, May 15 2008, Ralf Angeli wrote:
>>
>> Yes, this seems necessary.
>>
>> Something along this line.  WDYT?
>
>> +    (,(if (and (not (featurep 'xemacs)) (>= emacs-major-version 22))
>> +	  'open-file
>> +	'new-file)
>
> `open-file' and `new-file' need to be swapped.
>
>> +    (dired :image [,(if (and (not (featurep 'xemacs)) (>= emacs-major-version 22))
>> +			'diropen
>> +		      'open)
>
> Those should be strings.
>
> And `TeX-bar-TeX-buttons' and `TeX-bar-LaTeX-buttons' have to be adapted
> as well.  Either we provide both `new-file' and `open-file' in the
> default or we special-case them based on the Emacs version.  Again, I
> would not mind sparing some space by not offering `open-file' on Emacs
> 22. (c:

I've checked this in.

Re: AUCTeX tool-bar and icons

* Ralf Angeli (2008-05-14) writes:

> * Reiner Steib (2008-05-14) writes:
>
>> BTW, I don't think that duplication tool tips, images, etc. is a good
>> idea.
>
> Me neither.

One could probably just get the respective definition from the global
tool bar with someting like

(defun toolbarx-emacs-tool-bar-item (entry)
  "Return item from global tool bar corresponding to symbol ENTRY."
  (assq entry (cdr (default-value 'tool-bar-map))))

(defun toolbarx-emacs-tool-bar-item-prop (entry prop)
  "Return property PROP of the global tool bar item corresponding to ENTRY."
  (plist-get (toolbarx-emacs-tool-bar-item entry) prop))

and

(toolbarx-emacs-tool-bar-item-prop 'open-file :help)

But the returned forms would have to be evaled at run-time after the
global tool bar was created.  (At compile time the tool bar is not
defined.)  So before the current code becomes even more contorted I'll
leave this alone for now.

--

-- 

j ust starting

I am trying to latex a file.  All I get  is
Latex:  problems after [0] pages
and no .log file.

It does work on my laptop. 

Re: j ust starting

robert coleman <coleman <at> math.berkeley.edu> writes:

> I am trying to latex a file.  All I get  is
> Latex:  problems after [0] pages
> and no .log file.
>
> It does work on my laptop. 

Sounds like you don't have latex in your PATH.  Type C-c C-l after
trying to LaTeX a file and see in the buffer whether LaTeX starts up at
all.

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Restructuring of AUCTeX manual

Hi,

I'd like to restructure the manual a bit to make it more accessible.
Below you can find the main info menu and the table of contents taken
from the PDF output (first two sectioning levels only) as a proposal.

The idea is to have fewer entry points covering blocks of documentation
which are easily recognized by users (Editing, Display, Processing,
Customization) and reducing the clutter on the top level even further by
grouping auxiliary chapters (Copying, Introduction, Appendices,
Indices).

Let me know what you think.

Info menu
---------

* Copying::                     Copying
* Introduction::                Introduction to AUCTeX
* Editing::                     Editing the Document Sources
* Display::                     Controlling Screen Display
* Processing::                  Starting Processors, Viewers and Other Programs
* Customization::               Customization
* Appendices::                  Copying, Changes, Development, FAQ
* Indices::                     Indices

Table of contents
-----------------

Copying

changing parameters

dear auctex-wizards:

I am planning to write a preprocessor for latex, which does a couple of
things, most importantly:

    #    replaces % as the comment character
    \1,\2..    replaces #1, #2,.. as macro arguments
    \ns    replaces \#
    \nl    replaces \\
    \lcp    replaces \{
    \rcp    replaces \}
    \math{}    replaces $...$
    \be    replaces \[
     \ee    replaces \]
    $,%    become ordinary characters

and I also plan to extend the namespace of macros to include [0-9.:] by
mangling it into spelled out versions.  Maybe I want to allow ';' as a
terminating character that forces interpretation as '{\macro}'.

It is trivial to write a perl preprocessor to handle these changes.
the big advantage is that with these changes, writing a tex->anything
transcoder becomes a lot simpler.  (transcoder, not parser, of course.)

...except that I really would like to maintain basic auctex visibility while
editing.  would it be very difficult to define, say, '.pltx' which is 
like latex
mode, but knows about these changes?  the most important would be
to the change of comment character and recognize that $ sign is now

Re: changing parameters

* ivo welch (2008-08-13) writes:

> would it be very difficult to define, say, '.pltx' which is like latex
> mode, but knows about these changes?

You could probably define a derived mode similar to how it is done for
docTeX mode and adapt stuff like `comment-start' when it is initialized.

--

-- 
Ralf

looking for student programmer

auctex does seem a bit too daunting for me to hack.  so, I would like to 
hire someone for 3 hours to put together a hack that does the following 
(posted earlier):

I will use a preprocessor for latex, which does a couple of things, most importantly:

   #    replaces % as the comment character
   \1,\2..    replaces #1, #2,.. as macro arguments
   \ns    replaces \#
   \nl    replaces \\
   \lcp    replaces \{
   \rcp    replaces \}
   \math{}    replaces $...$
   \be    replaces \[
    \ee    replaces \]
   $,%    become ordinary characters

and I also plan to extend the namespace of macros to include [0-9.:] by
mangling it into spelled out versions.  Maybe I want to allow ';' as a
terminating character that forces interpretation as '{\macro}'.  Now, I need
a hack that changes the syntax highlighting in auctex.  preferably, it would
go into my .emacs file, so that future updates to auctex do not need internal
tweaking.

So, if you know how this would be done, and I can afford your help, I 
would love to hire you to do this.  please send me an email to ivo.welch 
at gmail.com .

Sincerely,

specific developer wanted

I would like to hire someone who is an experienced auctex hacker.  
Hopefully, it will be an hour of work, and I am offering $75 obo.  I 
need a local addon that I can stick into my .emacs file, that does the 
following:

* if the filename ends in .sltx, then load auctex but execute the 
following set of modifications:

# becomes the comment character, not %
$ and % lose their special meanings; they become ordinary characters
\m{...} has its arguments set as if its math mode.
\nl is like \\
\be is like \begin{equation}
\ee is like \end{equation}

I want indentation and highlighting to work right.  That's it.  It needs 
to go into my .emacs file, simply because I want it to survive the next 
auctex release upgrade.

Help appreciated.

Regards,

/iaw

Re: [AUCTeX] How to implement the function? Identify state of input method.

On Wednesday 20 August 2008, xiaopeng hu wrote:
> I use Ctrol to switch my input method between chinese and english.
> When I input $, coming in math mode,I need to automatically switch to
> english input method (push "Ctrl" key).
>
> First, I simulate a keystrike "t"+<space>, I will get a chinese character
> (not equal "t ")if my input method is chinese. Now I need Emacs
> automatically simulate a "Ctrl" key to switch to english input method.
> All of these is just after when I input $.
>
> How to implement the function?
>
> Thanks

I have attached a minor mode that changes the input encoding when 
entering and exiting math-mode or after a backslash. Copy it to a directory 
that is in the emacs load path (such as /usr/share/emacs/site-lisp/) and add:

(autoload 'latex-i18n-mode "latex-i18n" t)
(add-hook 'LaTeX-mode-hook 'latex-i18n-mode)

to ~/.emacs.

Hope this helps.

_______________________________________________
auctex-devel mailing list
auctex-devel <at> gnu.org