If the problem is to define a custom environment that one can redefine, once and for all, as, say, either gather or gather*, as the OP noted in one of her/his comments (switching from gather to align, or vice versa, seems much less sensible, of course!), it should be noted that this—I repeat, for an environment—is possible, thanks to the code that Michael J. Downes wrote some fifteen/twenty years ago and that, after having being integrated into the amsmath package, formed the base of the environs package. Look at the following code for a working example:
% My standard header for TeX.SX answers:
\documentclass[a4paper]{article} % To avoid confusion, let us explicitly
% declare the paper format.
\usepackage[T1]{fontenc} % Not always necessary, but recommended.
% End of standard header. What follows pertains to the problem at hand.
\usepackage{amsmath}
\newenvironment*{mygather}{\gather}{\endgather}
% \newenvironment*{mygather}{\csname gather*\endcsname}{\endgather}
\newenvironment*{myalign}{\align}{\endalign}
% \newenvironment*{myalign}{\csname align*\endcsname}{\endalign}
\begin{document}
A customized \texttt{gather} environment:
\begin{mygather}
1+1+1+1 = 4\\
\frac{\sqrt{y}}{x^2} = a
\end{mygather}
A customized \texttt{align} environment:
\begin{myalign}
1+1+1+1 &= 4\\
\frac{\sqrt{y}}{x^2} &= a
\end{myalign}
\end{document}
You can comment out the two lines that say
\newenvironment*{mygather}{\gather}{\endgather}
and
\newenvironment*{myalign}{\align}{\endalign}
and uncomment in their place those that read, respectively,
% \newenvironment*{mygather}{\csname gather*\endcsname}{\endgather}
and
% \newenvironment*{myalign}{\csname align*\endcsname}{\endalign}
and check that everything works as expected.
The following points are worth remarking:
It is not necessary to say, for example,
\newenvironment*{myalign}
{\csname align*\endcsname}
{\csname endalign*\endcsname}
because \csname endalign*\endcsname and \endalign,
as well as \csname endgather*\endcsname and \endgather,
are perfect synonyms.
It would probably seem more obvious to write something like
\newenvironment*{mygather}{\begin{gather}}{\end{gather}}
but this does not work.
The benefit of a markup like, say,
\begin{mygather} ... \end{mygather}
over
\bgather ... \egather
is that the former integrates into LaTeX’s environment system,
taking advantage of its name-checking facilities; thus, if you
misspell the name mygather in the \end declaration, you’ll get a
meaningful error message. On the other hand, if you misspell an
argument delimiter like \egather, (La)TeX will swallow up the rest
of your file and then, very likely, halt with some mysterious error
message. (Of course, we are assuming that it is much more unlikely
to misspell the \end keyword itself, also because many editors will
supply it automatically.)
texdoc technotewill open the documentation then see section 6 "why can't I use abbreviations"... or see the file here but it is a bad idea to hide environment syntax even for environments where it works. – David Carlisle Jun 08 '17 at 06:51\bg,\egit can not select the environment or syntax highlight the contents as mathematics or do anything useful. – David Carlisle Jun 08 '17 at 06:53gatherorgather*; indeed, while\newenvironment*{bg}{\begin{gather}}{\end{gather}}does not compile,\newenvironment*{bg}{\gather}{\endgather}works as expected, and you can subsequently change the definition to\newenvironment*{bg}{\csname gather*\endcsname}{\endgather}(note that\csname endgather*\endcsnameis the same as\endgather). Are you interested in an answer going in this directon? – GuM Jun 08 '17 at 15:07\begin{align} \end{align}than \ba got to end ... \ea – David Carlisle Jun 08 '17 at 16:05\begin{myg} ... \end{myg}integrates into LaTeX’s environment system, taking advantage of its name-checking facilities; thus, if you misspell the namemygin the\enddeclaration, you’ll get a meaningful error message. On the other hand, if you misspell an argument delimiter, (La)TeX will swallow up the rest of your file and then, very likely, halt with some mysterious error message. (Of course, we are assuming that it is much more unlikely to misspell the\endkeyword itself, also because many editor will supply it automatically.) – GuM Jun 08 '17 at 20:39